[Seaside] Seaside as backend of apache

[Boris Popov]

Hey, I just came across lighttpd today as well, is it really that much
better than Apache performance-wise? Pretty much the only things we use
are rewrites, SSL, proxying and mod_deflate.

-Boris

-- 
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
http://tinyurl.com/r7uw4

boris at deepcovelabs.com

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> bounces at lists.squeakfoundation.org] On Behalf Of Avi Bryant
> Sent: Monday, March 12, 2007 4:50 PM
> To: Seaside - general discussion
> Subject: Re: [Seaside] Seaside as backend of apache
> 
> On 3/12/07, Martin Beck <martin.beck at hpi.uni-potsdam.de> wrote:
> > However, another possiblity would be to use FastCGI. There exists a
> package on
> > SqueakMap and squeaksource.com: fcgi. Unfortunately Apache doesn't
seem
> to
> > support fastcgi by its newest version 2.2 (although there is a
> development
> > package), but with e.g. Lighttpd you can get enormous speed
advantages.
> 
> Can you document these speed advantages?  I've never had the sense
> that Comanche/WAKom was much of a bottleneck, but I'd love to see
> numbers.
> 
> Avi
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside