James,
I am not sure if there is a "standard" approach, but here is one that worked
quite good for me in a computer based learning application (using patient
management problems): i divided my application in several layers, i used
cl-http only at the interface layer. I authenticated users in the interface
layer and passed data about user and action to the application layer , which
stored all necessary data in a user (history) model, where i had instances
of my own user class, each of these corresponded to one instance of a
cl-http user. I used a simple planner that looked at the action and the user
model to determine a response (E.G. return requested data, ask user a
question before returning the requested data, inform user that requested
data had already been requested). I had one action (starting to see a new
patient) which i could use to purge the data accumulated for one user, this
way i could release resources. This also allowed my to retain state across
sessions: a user could create a bookmark, log out, go to the bookmarked url
a few days later, log in and go on where (s)he left.
Andre
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.