Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling
 
PerlMonks  

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

by Matts (Deacon)
on Dec 15, 2002 at 18:10 UTC ( #220032=note: print w/replies, xml ) Need Help??


in reply to Re: POE::Component::Server::HTTP: The _signal event is deprecated
in thread POE::Component::Server::HTTP: The _signal event is deprecated

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.

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

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://220032]
help
Chatterbox?
[ambrus]: Hopefull the object isn't kept alive, the events are processed immediately, but you'd have to read a lot of source code to be sure about that.
[Corion]: ambrus: I think both of AnyEvent and Prima are pretty tight in their memory management because they both are cooperative multitasking and (I think) both use the Perl memory management for managing things
[Corion]: ambrus: And for Windows, I don't think that Prima knows if there still are messages queued for an object (in the Windows message loop). Finding that out would take lots of effort for little gain
[ambrus]: And even if this works, I'm still not sure you can't get double timeouts from a Timer.
[ambrus]: Corion: well Prima::Object says something like that the cleanup method will send an onDestory message and that you can't get more messages after cleanup, or something.
[Corion]: ambrus: Yeah - I don't think the deep source dive will be necessary if things are implemented as simple as they could be :)) And hopefully I won't need (more) timely object destruction. I can update the screen at 60Hz and hopefully even do HTTP ...
[Corion]: ... transfers in the background. Now that I think about it, this maybe even means that I can run the OpenGL filters on Youtube input :)
[ambrus]: Corion: I mentioned that the unix event loop of Prima always wakes up at least once every 0.2 seconds. Have you found out whether the win32 event loop of Prima does that too?
[Corion]: ambrus: Hmm - I would assume that the onDestroy message is sent from the destructor and doesn't go through the messageloop, but maybe it is sent when a window gets destroyed but all components are still alive...
[ambrus]: Corion: partly deep source dive, partly just conservative coding even if it adds an overhead.

How do I use this? | Other CB clients
Other Users?
Others studying the Monastery: (8)
As of 2016-12-09 10:25 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    On a regular basis, I'm most likely to spy upon:













    Results (150 votes). Check out past polls.