[Seaside] Re: Re: Swazoo as reverse proxy?

[Boris Popov]

Both serve content from libraries well enough, did you mean some other static content? Dumping those resources to the front end web server is usually done only for larger deployments as an optimization...

Cheers!

-Boris (via BlackBerry)

----- Original Message -----
From: seaside-bounces at lists.squeakfoundation.org <seaside-bounces at lists.squeakfoundation.org>
To: seaside at lists.squeakfoundation.org <seaside at lists.squeakfoundation.org>
Sent: Sat Feb 09 14:28:12 2008
Subject: [Seaside] Re: Re: Swazoo as reverse proxy?

"Boris Popov" <boris at deepcovelabs.com> wrote

> Well, for internal deployments of this small scale that don't need ssl and 
> other advanced features Swazoo, Kom and others are already good enough, 
> isn't it?
>

Dunno. e.g. Does Swazoo server static content? I don't think Kom does. Not 
sure what other "features" make or don't make sense, and I do understand the 
points about not re-inventing Apache.

Unsure ... Sophie 



_______________________________________________
seaside mailing list
seaside at lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20080209/9e06aaca/attachment.htm