[Seaside] About Seaside 3.0

Boris Popov boris at deepcovelabs.com
Sun Jul 13 03:14:49 UTC 2008

Also, further up the scale you have load balancer farms that offload all that boring stuff and proxy the rest to your application, be it seaside or ruby or whatnot. There's a reason they exist and we shouldn't hesitate to delegate a bit and focus on the stuff that makes a real difference.


-Boris (via BlackBerry)

----- Original Message -----
From: seaside-bounces at lists.squeakfoundation.org <seaside-bounces at lists.squeakfoundation.org>
To: 'Seaside - general discussion' <seaside at lists.squeakfoundation.org>
Sent: Sat Jul 12 20:10:52 2008
Subject: RE: [Seaside] About Seaside 3.0

> Apache rewriting is no nice solution.

Many would disagree.

> For example, you can't get the client 
> certificate in your application. 

That might be a good reason, I'll grant you that one.

> Performance is bad. 

Hardly an argument for a moving to an even slower single threaded non
scaleable Smalltalk web server and tying it up doing boring stuff like
serving static content while chewing up you're very limited application
resources which have to do all their work on the same thread.

> And I think the client IP is lost as well (but not sure with that...) 

Not true at all.  

Ramon Leon

seaside mailing list
seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20080712/d878bb1f/attachment-0001.htm

More information about the seaside mailing list