On Apr 6, 2008, at 12:55 PM, Jonathan Rockway wrote:
* On Sun, Apr 06 2008, Andy Grundman wrote:
On Apr 6, 2008, at 3:36 AM, Kaare Rasmussen wrote:
little bit. I was disappointed in the POE engine and came to the
conclusion that POE, while tons of fun to use, is not the right
Just when POE went 1.0! Not fair!!
POE rocks, but a single process just doesn't work for Catalyst,
because the entire time your application code is running, the process
is blocked. Multiple processes is really the only way to go for a
web
server. It may be possible to do some crazy things with something
like Coro but at a severe cost to performance.
Or Poco::Generic. That will allow you to (automatically) run Catalyst
in a separate (persistent) process. Prepare a few of those when the
server starts, and you have an event-based request acceptor that won't
block.
This is what I started to do with a Sprocket-based engine, but it
would have to proxy all data through the parent non-blocking process,
and you just aren't going to get the same level of performance doing
it that way vs. having each child accept() on the socket directly.
_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
