> Nikolaos,
>
> i think a combination of what we discussed might work.
>
> if a request comes it, check on getsession.isNew().
> if this is a new session, then check if the user already has a
> session from any previous browser. this will be from the hashtable where
you
> would be storing the ip-address of the user and the user-object. If there
is
> an object there, then delete it from memory. Add the new session with a
new
> user-id(integer from 1 - 9999).
> If getsession.isNew() returns false, this is an existing session,
> however it is posible that this session is an older session. to check
this,
> query on the hashtable whether the session is still the latest. If you do
> not find it there then u must hv deleted it (from above) and u can assume
> that it is an older session. If you find it, then this is the latest and
> probably the only session.
>
> There would be an issue here. If the session is an existing session,
> then you will hv to query with the unique integer and if it is a new
session
> then you will have to query n the ip-address. This can be worked out when
> you are implementing it(?)
>
> As for the ip-address, i think it would work if you plan to use it
only
> for one full session. Anybody on the list would have some more input on
> ths(?)
> I would suggest that you write a dummy servlt and check it out. Of
> course it all depends upon whether the ip-addres can be used as the unique
> identifying attribute of the user across multiple sessions in idfferent
> browsers...
>
> Raaj.
>
> ----- Original Message -----
> From: Nikolaos Giannopoulos <[EMAIL PROTECTED]>
> To: 'Rajendra Mishra' <[EMAIL PROTECTED]>
> Cc: Servlet Interest Technology. <[EMAIL PROTECTED]>
> Sent: Thursday, January 13, 2000 2:22 PM
> Subject: RE: Is Global Session Possible?
>
>
> >
> >
> > On Thursday, January 13, 2000 10:44 PM, Rajendra Mishra
> > [SMTP:[EMAIL PROTECTED]] wrote:
> > > Nikolaos,
> > > I am still at a loss to understand what exactly you are trying to
> > > remember here. Do you want the user-id to be persistent across *all*
> > session
> > > for the whole life-time of that user?(pardon my pun). If that is the
> > case,
> > > then the soln of using the IP-Address as the id wouldn't 't work. My
> > machine
> > > is assigned a new ip-address every-time i log on from my ISP.
> >
> > No. I don't care about the "life time" of the user (in this context of
> > course)
> >
> > > My suggestion was based on the assumption that you want to store
the
> > > user-id only for a temporary time till the time the user has an
instance
> > of
> > > the browser open. the moment he closes the browser, the sesion is
closed
> > and
> > > hence the user-id is deleted from memory. then when he opens another
> > > session, the user is given another user-id. If this is not true, then
i
> > am
> > > sorry. i led you towards an incorrect soln.
> >
> > Yes. This is what I'd like to do (i.e. store the id for a temporary
time).
> > BUT my problem seems to be what key I can use that will apply to the
user
> > in cases where:
> >
> > (1) he/she sticks to one browser (e.g. IE) and while accessing our site
> > does not change browser. This can be solved with cookies or URL
> re-writing
> > since these mechanisms work "somewhat" for a given browser.
> >
> > (2) he/she spawns multiple windows from one browser while accessing our
> web
> > site. This seems to be an issue for IE w.r.t. sessions since IE seems
to
> > cause the creation of new sessions. This too though can probably be
> solved
> > with URL re-writing or writing/reading specific cookie information.
> >
> > (3) he/she launches more than one browser "on the same system" (e.g. IE
> and
> > NN) while accessing our site and switches between browser apps. This
area
> > requires something more.
> >
> > It is (3) that I am concerned with... I would like to identify the
launch
> > of the second (AND subsequent) browser(s) and track them as being the
same
> > user. I am not sure that their IP address would do it - though I may be
> > wrong.
> >
> > IN a nut shell we want to restrict our web site page from ever having
more
> > than one active window (session), be it from multiple browsers, spawned
> > windows, etc..., for a given user at a time. We will most likely make
> the
> > most recent window (session) the one that stays active and invalidate
any
> > previous ones.
> >
> > e.g. User goes to our site, accesses our web page. Things start
> > happenning. He/she spawns another window. Things in new window start
> > happening and previous window stops doing anything. User launches
another
> > browser and accesses our site. New browser window has things start
> > happening and previous browser spawned window things stop happening.
> > etc....
> >
> > Hope this clarifies things a bit....
> >
> > ---Nikolaos
> >
> >
> > > Raaj.
> > >
> > >
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
