Re: [WWdevel] Preserving state on the server (was: SetMaker is slow!)

[Michael G. <ga...@ma...>]

> think the general gist of it is like this:
>
> So you have state objects in the database (or in memory, or
> whatever). They consist of an ID number and an arbitrary number of
> key/value pairs. The state IDs should be universally unique and
> unpredictable.
>

Is there any reason the key and the stateID need to be different?  
I've always
rather thought of the key as being a stateID.  One difference is that  
the key gets updated
from time to time and perhaps you'd like the stateID to persist longer.

-- Mike