Re: POE::Component::Server::HTTP: The _signal event is deprecated

sig() is not defined in the immediate class you used, but defined in POE::Kernel. What you need to do is to first create a POE::Kernel object, say $kernel, then:

$kernel->sig($signal_name, $state_name);
[download]

Give a try.

But I do think POE should provide better and more clear documentation, at least say something like "please see POE::Kernel for details about how to use sig()", if they don't want people to reconsider :-) especially when standard Perl distribution itself is getting better.

Comment on Re: POE::Component::Server::HTTP: The _signal event is deprecated Download Code

Replies are listed 'Best First'.
Re: Re: POE::Component::Server::HTTP: The _signal event is deprecated by Matts (Deacon) on Dec 15, 2002 at 18:10 UTC
This is incredibly misinformed. Do not, as this poster suggests, reconsider using POE. It's pretty well accepted that Perl 6 is at least another year away, and for widespread use I would expect it to be 2 or 3 years away (think about all the modules that will probably need porting). That's a long time to wait for a new programming language to be widely usable. I'm not suggesting that Perl 6 isn't going to be chock full of good ideas, but it's not here yet, and until it is a regular day-to-day coder simply can't consider it as an alternative option. Secondly, yes Perl 5.8 supports pretty stable threads, but there are still some major issues with them, for example creating a thread under iThreads is several orders of magnitude slower than forking a separate process. For other issues follow the perl5-porters mailing list, or grep the archives for Elizabeth Mattijsen's posts. POE however is here, it works, and it does what its supposed to do really really well.	[reply]

Replies are listed 'Best First'.

Re: Re: POE::Component::Server::HTTP: The _signal event is deprecated
by Matts (Deacon) on Dec 15, 2002 at 18:10 UTC

It's pretty well accepted that Perl 6 is at least another year away, and for widespread use I would expect it to be 2 or 3 years away (think about all the modules that will probably need porting). That's a long time to wait for a new programming language to be widely usable. I'm not suggesting that Perl 6 isn't going to be chock full of good ideas, but it's not here yet, and until it is a regular day-to-day coder simply can't consider it as an alternative option.

Secondly, yes Perl 5.8 supports pretty stable threads, but there are still some major issues with them, for example creating a thread under iThreads is several orders of magnitude slower than forking a separate process. For other issues follow the perl5-porters mailing list, or grep the archives for Elizabeth Mattijsen's posts.

POE however is here, it works, and it does what its supposed to do really really well.

[reply]