If Cookies aren't enabled, then the backend cookie feature wouldn't be any different from the existing session handling. (you can still configure a session database based on URL/PARAM/IP...) rand_backend would return a random backend (as it always had) instead of finding an answer in a cookie.
Since I use cookie based session affinity, everything would fall apart without cookies anyway. I can't see any way this method of tracking would work for the others (URL/PARAM) without rewriting request content, which isn't likely to ever be a pound feature. :) So if you aren't using cookies, this feature doesn't hurt anything. If you are using cookies, you can use Session Cookie, this feature, or both. Joe > -----Original Message----- > From: Robert Segall [mailto:[email protected]] > Sent: Thursday, January 13, 2011 12:55 PM > To: [email protected] > Subject: RE: [Pound Mailing List] RE: Website stalls every 60 seconds > > On Mon, 2011-01-03 at 20:18 +0000, Joe Gooch wrote: > > I've implemented the "tag each request with the backend in the > browser instead of storing our sessions locally and incurring > concurrency costs" method of session tracking. Described in 5 below. > > > > Patch (against 2.6c) is at: > https://users.k12system.com/mrwizard/pound/pound_26_backend_cookies.pat > ch.bz2 > > > > Essentially the change to session handling is when it has to choose a > random backend (i.e. didn't find in the hashtable, or > hashtable/sessions are disabled), it will check for the backend key > header and if found, it will use the backend that matches (if > possible). This can be used to turn off session handling entirely > (allowing pound to use backend keys to use backend stickyness), or to > augment session handling... For instance, if pound is restarted, the > session DB is cleared. Using the cookie in the browser, when sessions > are recreated, the correct backend will be chosen to resume their > sessions. > > > > > > Joe > > Many thanks for the path, Joe. > > I had a look at it, and I have one small objection: if I understand > correctly the whole thing stops working if a client does not support > cookies (because of user settings in a browser, or because of some > silly > API). > > We are now working at making the session cleaning somewhat more > granular > and efficient, so a bit of patience please... > -- > ?Robert Segall > Apsis GmbH > Postfach, Uetikon am See, CH-8707 > Tel: +41-32-512 30 19 > > > -- > To unsubscribe send an email with subject unsubscribe to > [email protected]. > Please contact [email protected] for questions. -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
