SPUG: client vs. server Re: BSD Sockets and perl
m3047 at inwa.net
Wed Jan 11 14:17:52 PST 2006
Client and server do retain some conventional meaning in blocking
situations, because the server is likely to block waiting for requests,
and the client is likely to block waiting for replies. Of course if the
server is capable of handling multiple requests simultaneously that
changes things, and if the client is requesting stuff from multiple
servers that changes things, and so forth.
Remember: "blocking" means.. blocking!
(Is this an appropriate time to mention UDP, and suggest they
evaluate the nature of the communication in terms of reliability which is
required as well as the reliability of the connection?)
(Also, what about expect?)
On Wed, 11 Jan 2006, Mike Schuh wrote:
> On Wed, 11 Jan 2006, David S.Patterson wrote:
> >So you're saying either the client or server can read or write to each
> >other, blocking or non-blocking, with the same basic functions once the
> >connection is established?
> "client" and "server" merely indicate who called whom. Think phone calls:
> the client calls the server but after that either may talk or both.
> Heck, neither could say anything - this could serve as an interesting way
> to monitor connectivity.
More information about the spug-list