[Seaside] Starting a site
boris at deepcovelabs.com
Fri Aug 24 21:41:57 UTC 2007
Please don't get me wrong, I'm not pushing for it, as a matter of fact chances are we'll switch to using Opentalk when it's ready anyway.
Having said that I think it is important for me to try to relay my point across as clearly as possible. We have a Seaside gateway that is deployed in X headless services on Y machines, all of varying configurations as far as their interfaces go. This cluster of machines is fronted by an F5 load balancer which essentially serves as an outer HTTP server with active caching capabilities for static resources, SSL offload and such. When new machine is added to the cluster it has X number of services on it each on its own port bound to all interfaces on that machine. In managed environments these are all imaged from the same source, configured by DHCP and their IPs added to load balancing cluster by administrative staff. The effort should really stop there, so I want a simple Smalltalk web server that binds to 0.0.0.0:p1,p2,pX and lets outside server(s) deal with actual configuration, because I will never ever have more than a single Swazoo site running on a given port. Your point about Swazoo having all these wonderful capabilities is well taken, what I was saying all along has more to do with people like me who do not and never will use them.
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
boris at deepcovelabs.com
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
> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> bounces at lists.squeakfoundation.org] On Behalf Of Janko Mivšek
> Sent: Friday, August 24, 2007 2:27 PM
> To: Seaside - general discussion
> Subject: Re: [Seaside] Starting a site
> Boris Popov wrote:
> > I do remember having this discussion as well, but in many situations you
> > are deploying behind a web server of some sorts by proxying the
> > Seaside/Swazoo combo, so IP configuration takes place there and
> > does not belong in the application, at least as far as I'm concerned.
> > So I want to bind to all addresses and let other people (or load
> > decide which ones they will route traffic to (this becomes even more
> > important in managed environments, which is where we are currently
> moving to).
> Well, you can spend quite an effort to configure Apache, load balancers
> etc, and you can't configure a simple host:ip:port combination on Swazoo?
> > In a nutshell given the following two choices, which would you prefer
> > if you wanted to listen on all interfaces?
> > A) Query the host for its interfaces and bind to all of them
> > B) Bind to 0.0.0.0
> Second one, but let me repeat again, besides HTTPServer listening to all
> interface you need to change hostname resolution to actually resolve
> nothing, that is to direct all requests to one and only one Site. We
> have a HTTP 1.1. compliant server here and just look at the standard and
> meaning of Host: header to undersand what I mean.
> Anyway, I'll look at that problem and how to make it as intrusive to
> existent Swazoo as possible soon.
> Best regards
> Janko Mivšek
> Smalltalk Web Application Server
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
More information about the seaside