The infamous 'session bleed' problem has happened to just about everyone.
It's not the static vars you need to worry about, rather, the nonstatic ones.
You can add whatever member vars you want to the child of an ND object
(typically a page).
Your session has exclusive access to the object during a web event. During
this time you can put a value into a var and then count on it during the rest
of the web event (not just the web event method, but all processing until the
page is displayed).
The problem is that when your web event ends, your session relinquishes the
object, and then ND gives it to another session. The var will contain
whatever value the first session put into it. ND does not clean it out. So
if the second session does not reset the var, and just uses it, it will get
the value set by the first session.
This has been discussed a lot, probably the #1 topic.
Salut,
Curt Springer, Team ND
>===== Original Message From [EMAIL PROTECTED] =====
>Hello,
>
>When we have many users using our application at the same time, they get
mixed up data. User 1 gets the data (pulled from a common db) which should
get
to user 2 and vice-versa.
>We checked that we don't have any static vars in our project and we still
get
everything all mixed up.
>
>Has this already happened to anyone?
>
>Regards,
>
>Pierre
>_________________________________________________________________________
>
>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]
_________________________________________________________________________
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]
