[Seaside] Starting a site

Boris Popov boris at deepcovelabs.com
Thu Aug 23 21:56:33 UTC 2007


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 balancers) decide which ones they will route traffic to (this becomes even more important in managed environments, which is where we are currently moving to).

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 individually
B) Bind to



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

Thank you.

> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> bounces at lists.squeakfoundation.org] On Behalf Of Janko Mivšek
> Sent: Thursday, August 23, 2007 2:49 PM
> To: Seaside - general discussion
> Subject: Re: [Seaside] Starting a site
> Boris,
> Boris Popov wrote:
> > Mostly because I just don't want to query the host to see which IPs
> > are available when is out there and waiting for me to use it :)
> > Single site restriction is just fine for ~100% of Seaside users anyway.
> We already had a debate on that. I think that most users are just happy
>   with default 'localhost' configuration when they start with Swazoo.
> Because immediately when you want to go public, you need to register
> your hostname and ip anyway! Not to mention when you are going to host
> on some server with many ip's, etc etc. What is missing of course is
> better documentation how to do that in Swazoo.
> I think that your case is a special one and I don't understand why
> should Swazoo be complicated to deal with just your special case?
> That doesn't mean that we won't introduce that feature in future Swazoo
> of course.
> Best regards
> Janko
> --
> Janko Mivšek
> AIDA/Web
> Smalltalk Web Application Server
> http://www.aidaweb.si
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list