dido:public:ra:xapend:xapend.a_glossary:c:client-server
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.a_glossary:c:client-server [2020/11/12 18:34] nick |
dido:public:ra:xapend:xapend.a_glossary:c:client-server [2021/10/04 10:23] (current) 118.71.190.79 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ==== Client-Server ==== | + | ===== Client-Server ===== |
| - | [[[[dido:public:ra:xapend.glossary| Return to Glossary ]] | + | [[dido:public:ra:xapend:xapend.a_glossary:start| Return to Glossary ]] |
| - | The Client-Server model helped developers address the [[dido:public:ra:xapend.glossary:s:scalable|scalability]] issues of the [[ddsf:private:cookbook:06_append:glossary:p:point-to-point|Point-to-Point]] [[ddsf:private:cookbook:06_append:glossary:c:communications_model|communication model]]. Client-server networks designate one special [[ddsf:private:cookbook:06_append:glossary:s:server|server]] node that connects simultaneously to many client nodes, as illustrated below. Client-server is a "many-to-one" communications architecture. | + | The Client-Server model helped developers address the [[dido:public:ra:xapend:xapend.a_glossary:s:scalable|scalability]] issues of the [[dido:public:ra:xapend:xapend.a_glossary:p:point-to-point|Point-to-Point]] [[dido:public:ra:xapend:xapend.a_glossary:c:communications_model|communication model]]. Client-server networks designate one special [[dido:public:ra:xapend:xapend.a_glossary:s:server|server]] node that connects simultaneously to many [[dido:public:ra:xapend:xapend.a_glossary:c:client|client]] nodes, as illustrated below. Client-server is a "many-to-one" communications architecture. |
| <figure> | <figure> | ||
| {{ :dido:public:ra:xapend.glossary:c:client_server_communications.png?300 |}} | {{ :dido:public:ra:xapend.glossary:c:client_server_communications.png?300 |}} | ||
| <caption>Client-Server Communication</caption> | <caption>Client-Server Communication</caption> | ||
| </figure> | </figure> | ||
| - | The client-server network architecture works best when information is centralized, such as in databases, transaction processing systems, and file servers. However, if information is being generated at multiple nodes, a client-server architecture requires that all information are sent to the server for later redistribution to the clients. This approach is inefficient and precludes deterministic communications, since the client does not know when new information is available. The time between when the information is available on the server, and when the client asks and receives it adds a variable [[ddsf:private:cookbook:06_append:glossary:l:latency|latency]] to the system. | + | The client-server network architecture works best when information is centralized, such as in databases, transaction processing systems, and file servers. However, if information is being generated at multiple [[dido:public:ra:xapend:xapend.a_glossary:n:node|nodes]], a client-server architecture requires that all information are sent to the server for later redistribution to the clients. This approach is inefficient and precludes deterministic communications, since the client does not know when new information is available. The time between when the information is available on the server, and when the client asks and receives it adds a variable [[dido:public:ra:xapend:xapend.a_glossary:l:latency|latency]] to the system. |
| Example of Client-Server Communication | Example of Client-Server Communication | ||
dido/public/ra/xapend/xapend.a_glossary/c/client-server.1605224075.txt.gz · Last modified: 2020/11/12 18:34 by nick
