Ian Bicking wrote: > This was discussed on the mailing list a while back -- "load > balancing" > or something was the subject. > > With your current setup, you'll do better to have a third server (or > dual use for one of your current servers), and have it redirect people > round-robin-style to www1.whatever, www2.whatever, etc. Then > users will > always go back to the same computer for their session. This > is what you > want, but round-robin DNS won't ensure they always go back to the same > server.
This should work well in most cases, and it's easy. The only flaw is that if someone visits www.whatever and gets redirected to www1.whatever, then later in the same session returns to the home page www.whatever then 50% of the time they will be redirected to www1.whatever where they can continue their session, and 50% of the time they will get redirected to www2.whatever where they will start a new session. In practice, you can probably live with this problem. And there's a way around the problem too. If WebKit has some way to tell that it has just been redirected to, it could clear out the session. Perhaps the redirector could add in an extra query value NewSession=1 which WebKit could detect and use to invalidate the session. So: http://www.whatever/Foo/Bar redirects to http://www1.whatever/Foo/Bar?NewSession=1 (or www2) In your SitePage.awake() you can put in code like this: if self.request().hasField('NewSession'): self.session().values().clear() to clear out the session variables if NewSession is set. - Geoff _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
