>Erik:
>
>>>There are lots of things that do require that state be saved, but this state is usually tied to a session. This can be handled with a custom state object, and persisted to a memo in a session table with wwXML's ObjectToXML method, and retrieved using its counterpart XMLToObject method.
>
>That sounds interesting. What kind of object is being saved as XML and what kind of information and for what purpose?
>



YOu might have a "purchase" object that stores information about a purchase in progress. An alternative to making the client carry around all of the data about the purchase from hit to hit, is to store some of this data in a session table. In WWWC, this is done with wwSession, and you store session variables to a memo field with its AddSessionVar (or something) method. You then retrieve that value with GetSessionVar (or something- I can't remember the exact method names without looking them up). But if you have a whole set of data that needs to be retreived and persisted on every hit, you can create a custom object whose properties hold the values you want to persist (sort of like a parameter object) and then persist the whole object to a memo with ObjectToXML. This way the client only needs to carry around his identifier, which is used to associate him with a session.