Lines Matching full:server

28 .\".ds RH "Client/Server Model
37 4. CLIENT/SERVER MODEL
43 is the client/server model. In this scheme client applications request
44 services from a server process. This implies an asymmetry in establishing
45 communication between the client and server which has been examined
47 between client and server, and consider some of the problems in developing
48 client and server applications.
50 The client and server require a well known set of conventions before
63 will first consider the properties of server processes, then
66 A server process normally listens at a well known address for
67 service requests. That is, the server process remains dormant
69 to the server's address. At such a time
70 the server process ``wakes up'' and services the client,
73 Alternative schemes which use a service server
74 may be used to eliminate a flock of server processes clogging the
78 ``internet super-server.'' \fIInetd\fP listens at a variety
81 listening, \fIinetd\fP executes the appropriate server program to handle the
103 example, the remote login server's main loop is of the form shown
125 /* Disassociate server from controlling terminal */
156 Figure 2. Remote login server.
160 The first step taken by the server is look up its service
181 Step two is to disassociate the server from the controlling
198 This step is important as the server will
201 once a server has disassociated itself it can no longer
205 Once a server has established a pristine environment, it
207 The \fIbind\fP call is required to insure the server listens
209 remote login server listens at a restricted port number, and must
235 An \fIaccept\fP call blocks the server until
245 in hand, the server then forks a child process and invokes
258 and server clearly in the code. The server is a passive entity,
263 by the client remote login process. As in the server process,
283 connection to the server at the requested host and start up the
288 bzero((char *)&server, sizeof (server));
289 bcopy(hp->h_addr, (char *) &server.sin_addr, hp->h_length);
290 server.sin_family = hp->h_addrtype;
291 server.sin_port = sp->s_port;
303 if (connect(s, (struct sockaddr *) &server, sizeof (server)) < 0) {
320 A user on any machine running the rwho server may find out
353 by rwho server processes on each machine. The same server
361 as all hosts must process each message, whether or not using an rwho server.
368 The rwho server, in a simplified form, is pictured in Figure
369 4. There are two separate tasks performed by the server. The
374 server process, then are time stamped with their arrival time
379 is prone to error as a server may be down while a host is actually
436 Figure 4. rwho server.
440 The second task performed by the server is to supply information
457 for a server will have no idea what machines are its
466 these neighbors. If each server has at least one neighbor supplied
469 are not (possibly) directly neighbors. If the server is able to
482 This would require a separate copy of the server at each host and