Re: IO::Select and correct way to detect client crashed?

Note: The code is an adaption of code provided by BroswerUK .

I utterly refute that assertion.

How you dare to claim that your non-functional, incorrectly designed, and horribly implemented single-threaded, event-driven, asynchronous server & client are an "adaption from" my functioning, multi-threaded, synchronous server and client is quite beyond my understanding.

The only elements they have in common -- the timing mechanism and the length-prefixed protocol -- are in no way responsible for the failures of your code!.

The code I supplied to you: works. It is your clumsy and incorrect adaption of it that is broken; so please do not attribute that to me.

(Yes. I am offended.)

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

RIP Neil Armstrong

Comment on Re: IO::Select and correct way to detect client crashed?

Replies are listed 'Best First'.
Re^2: IO::Select and correct way to detect client crashed? by flexvault (Monsignor) on Oct 18, 2012 at 21:47 UTC
BrowserUk, I apologize! Your code does work and that is why I linked to your code to show the world and you, that my 'changes' are mine, but still giving you credit for the initial code that put me in the right direction. That said, the above code works 100% in non-treading environment for 14 days plus with 64 clients with 16 cores at 100%. But with Perl threads on AIX and Linux, I haven't been able to keep the threaded code running for more than a day. I suspect the underlining thread libraries may be the problem or it's my lousy code. I'm looking for a solution with 'IO::Select' until I find the problem with my treaded code. Again I apologize. "Well done is better than well said." - Benjamin Franklin	[reply]
Re^3: IO::Select and correct way to detect client crashed? by BrowserUk (Patriarch) on Oct 19, 2012 at 03:05 UTC
I'm looking for a solution with 'IO::Select' until I find the problem with my treaded code. FWIW: to the best of my ability to determine, the latest version of IO::Select is simply broken. Whether this is confined to my platform or is universal I have no way to know. I'd much rather look at fixing your threads problem than working with IO::Select. With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. RIP Neil Armstrong	[reply]