Re: POE::Component::Server::TCP bug fixes, possibly incompatible

2009-07-16 Thread Chris 'BinGOs' Williams
On Wed, Jul 15, 2009 at 06:59:12PM -0800, Michael Fowler wrote: On Wed, Jul 15, 2009 at 04:08:48AM -0400, Rocco Caputo wrote: For starters, $_[ARG0] isn't guaranteed to contain anything in particular. Well, it's guaranteed to contain whatever was passed as the 'args' argument to the

Re: POE::Component::Server::TCP bug fixes, possibly incompatible

2009-07-16 Thread Nick Williams
Regarding the passing of the socket into clientconnected - I've wished for this in the past, in order to be able to modify TCP options on the socket, which didn't seem possible in the past... It would be nice if that was possible to get at this (either via some available API which I just haven't

Re: POE::Component::Server::TCP bug fixes, possibly incompatible

2009-07-16 Thread Ed W
Nick Williams wrote: Regarding the passing of the socket into clientconnected - I've wished for this in the past, in order to be able to modify TCP options on the socket, which didn't seem possible in the past... It would be nice if that was possible to get at this (either via some available API

Re: POE::Component::Server::TCP bug fixes, possibly incompatible

2009-07-16 Thread Chris 'BinGOs' Williams
On Thu, Jul 16, 2009 at 12:59:09PM +0100, Ed W wrote: Nick Williams wrote: Regarding the passing of the socket into clientconnected - I've wished for this in the past, in order to be able to modify TCP options on the socket, which didn't seem possible in the past... It would be nice if that

Re: POE::Component::Server::TCP bug fixes, possibly incompatible

2009-07-16 Thread Ed W
Chris 'BinGOs' Williams wrote: On Thu, Jul 16, 2009 at 12:59:09PM +0100, Ed W wrote: Nick Williams wrote: Regarding the passing of the socket into clientconnected - I've wished for this in the past, in order to be able to modify TCP options on the socket, which didn't seem possible in