The problem isn't directly with the use of session objects. ND
keeps these straight for you so that one session does not get access to
session objects of another session.
More likely, you are putting values into instance variables in objects
shared by multiple sessions, like CSpPage children. Each such object is
used exclusively by one session during a web event. If one session puts a
value into an instance variable, that value will be sitting there when the
next session takes control of the object.
This means that you should not use an instance variable in a web event
until after you have loaded it from a session value or from the request
parameters. Servlets are multi-threaded and present the same issue.
-- Curt Springer, Team NetDynamics
BTW this problem doesn't go away when you leave ND.
At 01:20 PM 6/30/00 +0200, Klaas Troost wrote:
>We also use session objects in our application, but we use the functions:
>CSpider.putUserSessionObject() and
>CSpider.getUserSessionObject(). till now we had no problems.
>
>I hope this work 4u2.
>
>
>
>
>_________________________________________________________________________
>To unsubscribe from this mailing list please send an email to:
>[EMAIL PROTECTED]
>Please remember to use the same email address you subscribed with.
>
>For help in using, subscribing, and unsubscribing to the discussion
>forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
>
>For dire need help, email: [EMAIL PROTECTED]
_________________________________________________________________________
To unsubscribe from this mailing list please send an email to:
[EMAIL PROTECTED]
Please remember to use the same email address you subscribed with.
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
