James Edward Gray II wrote:
# do work here, like: while (<$socket>) { print; } # or whatever
construct such as this should almost never be used in a network application.
this will potentially hung your application when the client and the server
use a different EOL sequence. when this happen, the client process won't
return so when you fork again, the number of process will keep going up
which will eventually fill up the process table and crash the machine.
<laughs> Obviously, that was the part NOT from the Cookbook.
For what it's worth, I did intend it just as an example, showing where to stick the IO code. You're very right though and I should have clarified the dangers.
Thanks,
James
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
