I really depends on how much work POE has to do for each child. We use POE and Net::Server for different applications and usually start with POE and drop to Net::Server when POE can't handle the overhead.
So you need to figure out how much work needs to be done and see if a single threaded process (which is what POE is) can do it. > -----Original Message----- > From: Corey Goldberg [mailto:[EMAIL PROTECTED] > Sent: Monday, July 05, 2004 8:24 PM > To: [EMAIL PROTECTED] > Subject: Re: POE scalability vs. forking > > > >POE can fork, look at the POE::Wheel::Run module or > >POE::Component::Child. > >These modules can do forking and management of those children. > > Thanks for the reply. But I am looking for the "exclusive or" ;) > Either using forks (outside of POE), or using POE and making > use of the event loop (without forking) > > -Corey > > > > > > ----------------------------------- > Corey Goldberg > [EMAIL PROTECTED] > [EMAIL PROTECTED] > [EMAIL PROTECTED] > ----------------------------------- > > >
