I'll answer directly into Mike's response. Thanks Mike by the way for
replying so fast
-----Message d'origine-----
De : Mike McKechnie <[EMAIL PROTECTED]>
� : Sylvain Roche <[EMAIL PROTECTED]>; [EMAIL PROTECTED]
<[EMAIL PROTECTED]>
Date : lundi 10 avril 2000 17:18
Objet : Re: mixing sessions with cookies, sessions with url rewriting
>As Jim Haungs is fond of saying, "the only interesting numbers are one and
>infinity". Designing a workaround for exactly two sessions could cause
>problems when you need to go to three...
>
Actually, this IS a matter of two servers, as long as I want one of them to
serve the cookies managed sessions, and the other to server the url rewrited
sessions.
>Also, note that if a user starts a new browser process, that browser will
>get a new session no matter what you do. In fact, that's how I support
>multiple sessions -- if people want multiple logins, they start up multiple
>browsers instead of doing file->newWindow.
Do you mean for example start once Netscape and then IE ? Because that's far
from what I want. I want them to be able to browse different part with
different windows, but they should all come from a file/new window
>
>In your case, you apparently want multiple sessions in the same browser
>instance -- much trickier.
That's it ;-) In fact, that it is exactly what happens when you browse with
multiple windows on x sites, which have different urls. The problem is also
much trickier I first thought, because it does work with cookies, as long as
the urls are different. But I may not be able to split this site in as many
different adresses than I need (potentially a whole ballpark). Part that may
not be separated will be in subdomain, and in this case, I may not be able
to use cookies. Hence, url rewriting
>Perhaps you could create a simple session
>management bean that listens for the session binding event, and initializes
>a Hashtable of sub-sessions? If you're using model2 architecture, you could
>guarantee that all served pages include a sub-session identifier in their
>URLs. I'm not sure how you'd support creation of new sessions -- perhaps
>through an explicit menu item in your app?
This is exactly the problem. As I use the same url (remember, subdomain) the
new sub-session would probably replace the session environment for all pages
for this domain, because the session cookie is linked with the url. I'm not
quite sure, so I will test it anyway.
Best regards
Sylvain
>
>_3
>M
>
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
