>I'm looking into revamping my biz classes to accomodate statelessness and I have the following question.
>
>I currently use a group of publically exposed properties (e.g. lAllowInsert, lAllowDelete, lAllowUpdate, lAllowNavigate, lRecordBOF, lRecordEOF, etc.) which are queried internally and externally as needed. Now, these properties have _access methods where rule code is written and, therefore, reevaluated whenever queried.
>
>Therefore, as long as the state of cursor(s) can be reestablished, the behavior of these properties should be consistent with statefull objects and no rework required. Yes / No / I Don't Know ?
>
>The other, and perhaps more important, question is how the hell to reestablish the entire state of a cursor? Sure, you can reestablish record pointers, but what about information concerning table buffered records - OLDVAL(), CURVAL(), EVALUATE()? Should all this stuff fly out the window? Should the client retain this information via some kind of state object or array?
>
>I'm kinda lost here and I have yet to find any detailed white papers concerning this subject.


To have truely stateless objects, you don't set properties...you pass everything as parameters. The method may need to set properties as it calls other methods, but the client should not set properties at all. You can never guarantee the value of a property from one call to the next.