On Mon, 20 Oct 2003 [EMAIL PROTECTED] wrote:
... If you
actually start another copy of IE, that does NOT have the same
non-persistant cookies, and its a different session.
Is this behavior the same for both Apache::Session and CGI::Session?
May I quote myself:
In either case, as long as the two 'windows' share the cookie on which
the
session state is based, they will be in the same session. :)
Perhaps I need to clarify.
Without some sort of repeating token, the server cannot correlate one page
request with another page request. There's only a loose correlation
outside of the token. Why? Because many people can use the same IP, and
the same session can (and does) use multiple separate server connections.
Hence, in order to correlate any sequence of requests into a session, it
has to identify the user somehow!
This is done by having the browser, in some manner send a token that the
server can use to identify that user uniquely.
I think the most precise answer that can be given is that when this token
is shared by both browsers/windows, and ONLY then, will they will both be
in the same session.
Otherwise, there is no correlation, they are not in the same session.
this is true regardless of what sessioning mechanism, program, library, or
utility you are using.
Does that answer the question?
Maybe you're really asking for the behavior of your particular browser
that you're using.
I do believe that both the libraries you inquired about utilize a normal,
non-persistant cookie for session tracking.
As to what the browsers do with it, depends on the browser.
Skylos
-thanks
On Mon, 20 Oct 2003 [EMAIL PROTECTED] wrote:
Can someone comment on some advantages/disadvantages?
Does opening a new browser causes a new session in either of the two?
well, in IE, cookes are relevant to processes, not to windows. That
is,
you can have one process with multiple windows (file->new->window)
that
all have the same non-persistant cookies, hence, sessions. If you
actually start another copy of IE, that does NOT have the same
non-persistant cookies, and its a different session.
In either case, as long as the two 'windows' share the cookie on which
the
session state is based, they will be in the same session. :)
Skylos