|
Posted by Michael Vilain on 10/09/87 11:36
In article <1136388203.146031.34770@f14g2000cwb.googlegroups.com>,
"Slav" <slawek_jarosz@engineer.com> wrote:
> OK, what you write makes sense. However, at work I am using the same
> type of setup. A user is authenticated, a session is started and the
> user can navigate through the online application. At work, I can have
> multiple IE browsers open and during the last 2 years, never have I
> seen the problem of the session switching between users. Even on my
> own application, I do not see this problem every time. It happens
> every so often. Meaning I had as many as 4 IE windows open connecting
> to my on-line application and never saw a switch. Then it happens out
> of the blue. Now the differences between my work application and
> private application:
> Work: Linux running Apache with a https sessions
> Home: Windows XP running Apache with no security
>
> Thanks again,
>
> Slav
>
> Michael Vilain wrote:
> > In article <1136346431.043985.98160@g43g2000cwa.googlegroups.com>,
> > > Slav
> >
> > If I understand your situation, if IE is running on the same machine
> > with the same IP address and user, I don't see a way to do what you're
> > trying to accomplish--separate instances using the same browser. Now,
> > if you have two different browsers (say, IE and FireFox), that would
> > probably work as cookies are usually stored in separate places. Or use
> > separate user accounts (if your OS allows multiple logins) as the cookie
> > files are in different directories. But the web server (and php) has no
> > way to distinguish connections coming from the same machine. Only the
> > client browser differentiates that. So, unless you use a different
> > user, browser, or machine, you're pretty much stuck with the behavior
> > you see.
> >
> > --
> > DeeDee, don't press that button! DeeDee! NO! Dee...
Note that you're using a different OS and probably not running IE on
Linux (or are you using it w/ WINE?). Anyway, running browsers on Linux
probably uses the process management features of a UNIX-like OS
(creating processes--forking a child--or creating and scheduling threads
to allow for SMP).
I can only speculate about the Linux system's behavior. Could it be
you're running multiple instances of the browser, _each with it's own
process virtual memory_? Or is the behavior of the browser you use to
fork a child process for each window rather than creating threads to
schedule. If that's the case, then you _are_ running different copies
of the browser in memory.
I don't know Microsoft's internals at all, but I'm guessing that when
you open multiple windows of IE on XP, you're running only one instance
of the browser with multiple windows, possibly with threads if Microsoft
implements such things in their OS. But a threaded application shares
it's memory amongst the threads which are scheduled by the kernel.
This is just a SWAG, so take it with several Kg of NaCl...
--
DeeDee, don't press that button! DeeDee! NO! Dee...
Navigation:
[Reply to this message]
|