the perl cookbook is very handy for this and should answer your questions and give all the examples you need. <br><br><a href="http://www.unix.org.ua/orelly/perl/cookbook/ch17_01.htm">http://www.unix.org.ua/orelly/perl/cookbook/ch17_01.htm
</a><br><br>note the mispelling of 'oreilly' in the URL <br><br><br><br><div><span class="gmail_quote">On 1/11/06, <b class="gmail_sendername">Mike Schuh</b> <<a href="mailto:schuh@farmdale.com">schuh@farmdale.com</a>> wrote:
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Wed, 11 Jan 2006, David S.Patterson wrote:<br><br>>So you're saying either the client or server can read or write to each
<br>>other, blocking or non-blocking, with the same basic functions once the<br>>connection is established?<br><br>"client" and "server" merely indicate who called whom. Think phone calls:<br>the client calls the server but after that either may talk or both.
<br>Heck, neither could say anything - this could serve as an interesting way<br>to monitor connectivity.<br><br>--<br>Mike Schuh -- Seattle, Washington USA<br><a href="http://www.farmdale.com">http://www.farmdale.com</a>
<br><br>_____________________________________________________________<br>Seattle Perl Users Group Mailing List<br> POST TO: <a href="mailto:spug-list@pm.org">spug-list@pm.org</a><br>SUBSCRIPTION: <a href="http://mail.pm.org/mailman/listinfo/spug-list">
http://mail.pm.org/mailman/listinfo/spug-list</a><br> MEETINGS: 3rd Tuesdays<br> WEB PAGE: <a href="http://seattleperl.org/">http://seattleperl.org/</a><br></blockquote></div><br>