[Seaside] About Seaside 3.0

Philippe Marschall philippe.marschall at gmail.com
Sun Jul 13 06:59:56 UTC 2008

You will have Apache as a frontend anyway because:
- there is to my knowledge no way to run Squeak on a privileged port
without giving it root rights
- there is to my knowledge no way to generate Apache style access logs
with Kom. The ones that can be read by a whole lot of tools like
- Apache will still be running when your image is long gone and can
serve a nice 503 page
- less bitching with your admin and security people

Second, HTTPS/SSL really eats CPU cycles. Thats why a lot of sites
like GMail use it only for login and then switch back to HTTP.

Once you have accepted that there will always be an Apache frontend
implementing a web server in Smalltalk doesn't make a whole lot of
sense anymore. Something like an AJP connector will do fine.


2008/7/13 Bill Schwab <BSchwab at anest.ufl.edu>:
> Philippe,
> Why?  That then forces users to set up Apache, and then configure it
> correctly.  Squeak/Pharo should be able to do SSL on its own, and can
> thanks to the cryptography group's efforts.  With some extra effort, it
> could serve secure pages on its own.  Just about any otherwise
> non-Seaside service could benefit from such a simple to manage secure
> web server.
> Bill
> Philippe Marschall philippe.marschall at gmail.com
> =================================
> SSL belongs into Apache not Comanche.
> Cheers
> Philippe
> Wilhelm K. Schwab, Ph.D.
> University of Florida
> Department of Anesthesiology
> PO Box 100254
> Gainesville, FL 32610-0254
> Email: bschwab at anest.ufl.edu
> Tel: (352) 846-1285
> FAX: (352) 392-7029
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list