PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Xi Chen
Sent: June 6, 2006 5:21 AM
To: wtr-general@rubyforge.org
Subject: [Wtr-general] BUG: New IE windows share session state with
existingopen windows
Hi Scott
I tried to run the following
ie_array = Array.new(3)
ie0 = WIN32OLE.new('Shell
There's another issue which may be affecting your test that is also NOT
a Watir bug.
Sessions are often set by having a server save a session ID cookie on
the IE's PC. For IE, these cookies are saved in a per-user directory.
If you run multiple IE's to the same site then the cookies can be
o
riginal Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David Schmidt
Sent: June 6, 2006 12:50 PM
To: wtr-general@rubyforge.org
Subject: Re: [Wtr-general] BUG: New IE windows share session state with
existingopen windows
There's another issue which may be affecting your
runs, just as they should.
Lonny Eachus
==
Subject:
Re: [Wtr-general] BUG: New IE windows share session state with
existingopen windows
From:
"Michael Bolton" <[EMAIL PROTECTED]>
On 6/6/06, Lonny Eachus <[EMAIL PROTECTED]> wrote:
Our group has also found that global variables can carry over between
separate runs of the same application, probably due to server caching.
If a global variable was set during one run of the application, and not
explicitly set to somet
d, and then completed. The program exits. The next http request
to come in is a different "session". We are not storing cookies or any
other "session" data in any way. Yet there is no doubt that global
variables were being preserved between two different "sessions"
On 6/7/06, Lonny Eachus <[EMAIL PROTECTED]> wrote:
We had a server set up using multiple Mongrels with a lighttpd front
end. A server will wait for an http request to come in, and fire off
our Rails application. The program exits when done (i.e., the
controller .rb runs to completion, no
>I see
three ways this could happen, there may be more: (1) The variable "global_foo"
is truly "global" on that server from the moment it is instantiated, and remains
in memory even when there is no "running code". This is contrary to the
way I understood globals to function . . . in which c
it is
intended behavior, using globals can cause problems if you are not
careful and AWARE of how they work in Ruby and Rails. Their behavior is
very poorly documented, where it is documented at all.
Lonny Eachus
==
Subject:
Re: [Wtr-general] BUG
Please do not take this comment the wrong way, but this is the second
time someone has mentioned -- to me -- that this might be an
"inappropriate" topic for this forum.
Please read the subject line again. Someone asked about "session
states" being "shared" . . . in the context of Watir. I rep
10 matches
Mail list logo