<html>
<body>
<P><FONT face="Verdana, Arial, Helvetica, sans-serif" size=3>James,</FONT></P>
<P><FONT face="Verdana, Arial, Helvetica, sans-serif" size=3>Your comments are well taken. I've done these kind of projects in the distant past in C/C++, and I was always confused by this.</FONT></P>
<P><FONT face="Verdana, Arial, Helvetica, sans-serif" size=3>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?</P>
<P>Tks,</P>
<P>-Pat</P>
<P><BR></FONT><FONT face="Verdana, Arial, Helvetica, sans-serif" size=3><BR><BR></FONT>------ Original Message ------<BR><B>Received: </B>Wed, 11 Jan 2006 10:58:14 AM PST<BR><B>From: </B>"James Moore" <james@banshee.com><BR><B>To: </B>"'David S.Patterson'" <david.s.patterson@usa.net>, <spug-list@pm.org><BR><B>Subject: </B>RE: SPUG: BSD Sockets and perl<BR><BR><BR></P>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid; WIDTH: 100%">You're describing the normal way to use sockets, so giving pointers to <BR>examples would be tough - 90% of the example code for sockets would work <BR>just fine. <BR><BR>Don't get hung up on the distinction between "clients" and "servers" - those <BR>concepts are higher-level abstractions that don't really mean much at the <BR>socket level. Once the connection is established you've got two peers <BR>speaking to each other, and designating one side the "server" may help you <BR>think about a problem but there's nothing going on to enforce that thought. <BR><BR>- James <BR><BR><BR></BLOCKQUOTE>
<br>
</body>
</html>