OK Joe
Thanks for the clear introduction to 'State'. I understand that the 'session
id' is stored in a cookie or in a cookieless environment it is included in
the request or query string.
My question really is how do people using the i store the information that
is related to that session ID, e.g. in server memory (by Session ID),
written to disk (out of state storage) or is there an application level of
State, again stored in server memory?.
Can 'State Objects' be stored in the Server Cache and retrieved from there,
if so what types of objects can be stored and how are they retrieved and
re-instantiated?. Is there an equivalent of ViewState as used in .NET? Of
course there is a painful overhead but that can't really be avoided.
I guess the answer differs depending on whether your using, RPG(le), PHP,
EGL or other.
- Maurice
Typically there's a session ID somewhere in the transaction that's used
to retrieve all the appropriate state information. The state
information is persisted (the fancy name for "written to disk") on every
request and then retrieved on the next request. As you might guess,
this adds significant overhead. It's particularly painful when you need
to re-open and reposition database cursors.
Joe
Just as a question
How do you all manage state in the HTTP stateless environment? What is
state?
Happy new year
Maurice O'Prey
midrange.com
