The inline states should be looked upon as keywords pointing to a
subroutine. So you shouldn't have a subroutine named create_subscription.
It should be "sub cr_sub". Hope that helps.
--
Rohan
On Mon, Aug 13, 2012 at 6:26 PM, Gokul Prasad wrote:
> Hi,
>
> When am running this poe program, inst
For simple accessors, you can also use Class::Accessor
package PoeWithAccessors;
use strict;
use warnings;
use base qw/ Class::Accessor /;
use POE::Session;
__PACKAGE__->mk_accessors(
qw/
state
connection
client_ip
/
);
sub spawn
{
my ( $class, $par
It looks like it was released on March 25th but Rocco chose today
to announce it!
--
Rohan
Matt Sickler wrote:
I too thought this was a joke, then I realized the timestamp was last night.
[virutal] BEERS for all involved! Great Job everyone!
On Tue, Apr 1, 2008 at 10:26 AM, Randal L. Schw
Matt Sickler wrote:
I just committed a change that adds get_input_handle and
get_output_handle methods to Wheel::ReadWrite. :)
Thats great! I can see the changes in Sourceforge. Will download
the tarball from there.
Thanks,
Rohan
On 5/23/07, Rohan Almeida <[EMAIL PROTECTED]>
place.
On 5/23/07, Matt Sickler <[EMAIL PROTECTED]> wrote:
> The component wouldnt be the one to provide access to it.
> You would need to patch POE::Wheel::ReadWrite to provide an accessor
> method to the input and output handles.
>
> On 5/22/07, Rohan Almeida <[EMAIL PRO
any situations ).
This breaks encapsulation and could change at no notice and its all your
fault.
A better question you need to ask is why do you need to get at the socket?
On 5/22/07, Rohan Almeida <[EMAIL PROTECTED]> wrote:
Hi,
Is there any way I can get access to the underlying socket w
Hi,
Is there any way I can get access to the underlying socket while
using PoCo::Server::TCP without using the Client* callbacks?
The docs say that the socket is only passed if I use the Acceptor
callback, which then means I have to create my own Wheel for
read/write and so on.
Again, $h
