Option 4) if no session cookie handling, then realm is ignored (maybe this is the most correct)
On Jan 14, 2008 3:33 PM, Andrea Chiumenti kiuma72@gmail.com wrote:
Edi, I've been able to make it work with url-rewriting, but I don't know how rewriting should behave when referencing other realms. options are
- append the sessionid for realm1 even to realm2 related resources (not
very correct). 2) append nothing if resources belong to realm 2. (correct and easy), but when navigate from realm1 to realm2 you'll loose the session if cookies are disabled. 3) handle a sort of parent session that holds all sessions in realms, and then handle the url rewriting... (this requires more work)
kiuma
On Jan 14, 2008 1:24 PM, Andrea Chiumenti kiuma72@gmail.com wrote:
Edi, As a Murphi Law confirmation, session handling with session encoded into request doesn't work :/, I'm working on it. Modifications are of course backward compatible!
The importance on separate sessions depends only on how a person want to use hunchentoot, it has sense only if someone want to use hunchentoot as an application server so having sessions bound do 'deployed' applications.
I'll make the realm patch work very soon, cu,
kiuma
On Jan 14, 2008 8:52 AM, Edi Weitz < edi@agharta.de > wrote:
On Wed, 9 Jan 2008 11:27:21 +0100, "Andrea Chiumenti" < kiuma72@gmail.com> wrote:
I've no idea on how to do with cookies disabled, because I'm relatively new to Hunchentoot
Well, as I already said, I currently don't have the time to do this, and I don't think it's a very important feature. So, you'll either have to send a complete and fully-tested patch that's backwards-compatible or you'll have to wait until I get around to do it myself.
Cheers, Edi. _______________________________________________ tbnl-devel site list tbnl-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel