Re: robust all-perl web server, was Re: asynchronous execution

2002-11-21 Thread Leon Brocard
Stephen Adkins sent the following bits through the ether:

  * Is there a robust all-perl web server?

I've done some work in the past for OpenFrame on making HTTP::Daemon
forking and preforking, and also using
POE::Component::Server::HTTP. To be honest, most of them were a pain
to get running. For $latest_web_project we have a small Perl program
which writes a custom httpd.conf (using TT2) and then starts apache
using apachectl. It's much simpler, faster to develop, and generally
more robust. YMMV.

Leon
-- 
Leon Brocard.http://www.astray.com/
scribot.http://www.scribot.com/

 Real men write self-modifying code



Re: robust all-perl web server, was Re: asynchronous execution

2002-11-21 Thread Leon Brocard
Nigel Hamilton sent the following bits through the ether:

 Howw did you find the speed of each solution under load? DId anyone 
 come out faster?

There wasn't much difference at all. The webserver does very little
work compared to my web app.

Leon
-- 
Leon Brocard.http://www.astray.com/
scribot.http://www.scribot.com/

 BROADCAST MESSAGE AT 4:45pm. Brain going down. IMMEDIATELY.



Re: robust all-perl web server, was Re: asynchronous execution

2002-11-20 Thread Chris Winters
On Wed, 2002-11-20 at 17:14, Stephen Adkins wrote:
 This brings up an interesting question ...
 
  * Is there a robust all-perl web server?
i.e. HTTP::Daemon combined with Net::Server?
HTTP::Daemon - an all-perl web server (single request at a time)
Net::Server - multi-process, lots of nice things that Apache has
 
 It would be somewhat analogous to how the Tomcat Java Servlet engine
 can act serve web requests directly without any need for Apache.
 Or if you want to knit it together with Apache, you can do so with
 mod_jk (similar to Perl with mod_perl).

You can use forking with HTTP::Daemon for handling multiple simultaneous
requests. I dunno about polling/select. I'd be curious to see a
pure-perl ithreaded HTTP::Daemon if one doesn't already exist.

As for using it with Apache, you'd probably be able to use mod_proxy as
recommended in the mod_perl guide: light Apache process for static
content up front which proxies dynamic requests to the heavier backend,
in this case HTTP::Daemon instead of mod_perl.

Chris

-- 
Chris Winters ([EMAIL PROTECTED])
Building enterprise-capable snack solutions since 1988.




robust all-perl web server, was Re: asynchronous execution

2002-11-20 Thread Stephen Adkins
At 04:55 PM 11/20/2002 -0500, Aaron Johnson wrote:
On Wed, 2002-11-20 at 14:55, Perrin Harkins wrote:
 Aaron Johnson wrote:

... in my case it allows
for automation/reports on non-mod_perl machines.  I have some clients
that don't want/allow mod_perl servers on their network, in fact I am
lucky just to get Perl on it so I have to be happy with what I get :)

Hi,

This brings up an interesting question ...

 * Is there a robust all-perl web server?
   i.e. HTTP::Daemon combined with Net::Server?
   HTTP::Daemon - an all-perl web server (single request at a time)
   Net::Server - multi-process, lots of nice things that Apache has

It would be somewhat analogous to how the Tomcat Java Servlet engine
can act serve web requests directly without any need for Apache.
Or if you want to knit it together with Apache, you can do so with
mod_jk (similar to Perl with mod_perl).

Stephen