On Jul 14, 2009, at 02:16, Michael Fowler wrote:
http://rt.cpan.org/Ticket/Display.html?id=47855
47855 requires a bit of discussion.
The problem is that the ClientConnected callback does not actually
receive a socket in ARG0. ARG0 has been spliced off in the
POE::Wheel::ReadWrite
Oops, I meant to send this to the list.
-- Forwarded message --
From: Larry Clapp la...@theclapp.org
Date: Wed, Jul 15, 2009 at 7:58 AM
Subject: Re: poe.perl.org down?
To: Phil Whelan phil...@gmail.com
On Tue, Jul 14, 2009 at 7:21 PM, Phil Whelan phil...@gmail.com wrote:
I
Out of memory again. I've rebooted and reconfigured Apache a little.
Sorry for the inconvenience.
--
Rocco Caputo - rcap...@pobox.com
On Jul 15, 2009, at 07:59, Larry Clapp wrote:
Oops, I meant to send this to the list.
-- Forwarded message --
From: Larry Clapp
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 POE::Session constructor, right? When the session is
constructed, 'args' is
On (07/15 18:59), Michael Fowler wrote:
The code I have that actually needs it would benefit from the clarity of
having the socket passed as ARG0. Whether or not this breaks some
possible future change in something...
Perhaps I'm misreading... What I'm hearing is you should change this
for
On Wed, Jul 15, 2009 at 11:18:03PM -0400, sungo wrote:
Perhaps I'm misreading... What I'm hearing is you should change this
for me, regardless of whether it breaks other people's code. Is that an
accurate summary?
No. That was in response to expanding ClientArgs into ARG0..$#_. I'm
