Your skill will accomplish what the force of many cannot |
|
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
I seem to have confused you a little. I'm not all that concerned about the sucess of the transmissions themselves, so I have no checks on any of the writing to the sockets, the only problem I had was a set of dead sockets that my server was holding on to un-necessaraly. True I could add greater destinction between what went wrong in the read set, and I may do that at some point, but as it seems to work now, I see no need. As for the IO::Select thing, it is only being used as a "this socket has something to say" indicator. The expected length is determined by a 4 digit number that prefixes the message. It's also possible I'm mis-understanding your advice, if so please explain more fully. My code doesn't have bugs, it just develops random features. Flame ~ Lead Programmer: GMS (DOWN) | GMS (DOWN) In reply to Re: Re: Detecting a closed socket
by Flame
|
|