|The stupid question is the question not asked|
Non-Blocking Socketsby Anonymous Monk
|on Sep 20, 2003 at 14:02 UTC||Need Help??|
Anonymous Monk has asked for the
wisdom of the Perl Monks concerning the following question:
From the perl cookbook, i am using the following code to make a socket nonblocking.
Sometimes this actually kills the server while there are still active connections to it. So, instead of doing an "or die" i need to handle this a different way.
My question is 2 fold.
1) What causes this to fail? Is it server side, client side, or both?
2) Whats the best way to handle this? Passing it to another function to clean everything up in regards to that one socket?