>Currently, my bizobjs have cursor state properties (e.g. lCursorModified, nUpdateConflict, lCursorEOF, lCursorBOF, lAllowNavigate, lAllowDelete, lAllowAdd... etc.) which change via rules in their _access methods and are queried as needed.
>
>While I haven't had the time to do so yet (have'nt had the need yet, I need to come up with some sort of mechanism to retain cursor states - maybe a state object with the corresponding cursor state properties and SetState() / GetState() methods.
>
>Don't know yet - just thinking out loud.

Jeff,

Keep on thinking because the requirement fior statelessness is not the result of MTS. It is the result of how the internet access works. Your server is getting hits from different users adn the resources to create and maintain a business object for every user is prohibitive in all but the smallest (number of hits) web sites. You simply can't afford to have a user visit create an object adn tehn hold that object in state for that user. You have to design the web interface so each request for data provides all of the information for the business object to get that data without knowing anything about the last visit. Remember user #1 may initially vists the site and get access to BO#1 but eh next submit that user#1 sends may hit BO#8.