- From: DEWEERDT Frederik FTR&D <frederik.deweerdt@rd.francetelecom.com>
- Date: Thu, 16 Aug 2001 11:10:25 +0200
- To: "Danny Ayers" <danny@isacat.net>, "Naresh Jain" <narej@microsoft.com>, <www-talk@w3.org>
Le Jeudi 16 Août 2001 11:13, Danny Ayers a écrit : > Hi Naresh (and all). > > >I think it is possible to achieve. If you use Apache JServ for > >example, your client will be assigned a session ID. This session > > will be associated to the box that first served it, so incoming > > requests with this session ID (a cookie in fact) will be served > > by the original box. > > Hmm - I don't think you need cookies at all, if you maintain > session information on the server(s) then it it is possible to > specify which box If you don't use cookies, how is your session information going to be identified ? I'm pretty sure that PHP, JSP and so on rely on cookies for session identification. To be precise there might be another solution. It would be to add an extra header to your HTTP header. This as the advantage to be invisible to the user (ie. no cookie blocking problem). But it also as its drawback : you will have to implement the session<->box association by your own (ie. you will have to modify an existing product). > deals with whatever comms come your way. The following is the key point : > >IMHO the aswer to your question depends on the architecture you > > rely on. > > If you could supply details of the architecture you are using, a > more specific answer might be forthcoming ;-) > > Cheers, > Danny. -- F.Deweerdt frederik.deweerdt@rd.francetelecom.com
Received on Thursday, 16 August 2001 05:15:17 UTC