Forum Moderators: coopster
Web developing is _stateless_, and it appears you don't fully grasp what this means.
The only way that data can be passed between users (or indeed from page to page for the _same_ user) is to maintain state in some way (usually done by sessions and a cookie for each user), or of course by using permanent storage such as files or a database.
Data _can_ be passed between different users, but this is generally either due to a programming error (like posting a link somewhere with a session ID in the URL, or possibly a faulty implementation of a shared memory cache) or deliberate by design, but never by static variables.
[edited by: FalseDawn at 2:47 pm (utc) on Aug. 6, 2006]
I've always understood HTTP to be stateless but I don't know how one can say "Web Developing" is stateless. If, through my actions, a process begins to run on the server, it's feasible that the process could still be running when another user attempts to run it. Otherwise, we wouldn't need to do things like lock tables.
So, really, I don't think my question is so much about the stateless nature of HTTP, but rather how a server treats the static keyword. Specifically, if somebody attempts to execute a script while it is being run by another user, can I be sure they will not have access to static members created by that user, and why?
Thanks again for the quick response!
can one visitor get a static property value that was set by the actions of another?