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 something else on the next run, then it would (often? always?) retain the value from the previous run. Whether this behavior is by design or not is moot; it exists and it is something to watch out for.

Lesson here: Do not use global variables unless you have to, and expect this behavior if you do. Instance variables, however, do get re-initialized between 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]>
Date:
Tue, 6 Jun 2006 13:34:27 -0400

That's a good point if cookies are involved, for sure.  Even when they're
not involved, there can be some weirdnesses, too.  I remember that Firefox's
behaviour, in terms of session ID, is different; I don't remember how it's
different, though.

---Michael B. 
  

_______________________________________________
Wtr-general mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-general

Reply via email to