Hi,
you could use session's metadata to store user-relative data (provided
that they are serializable) when she/he successfully logs in. IMHO
creating a custom WebRequestCycle is not necessary.
I plan to implement a project with AuthenticatedWebApplication. The users have
to sign up for an account. My question is regarding the user data that I have
to load during each request of the single pages.
The project will be as follows:
(1) User logs into the system
(2) The dashboard will be loaded
(3) The user clicks the menu and gets a different representation of the
information
I would like to know the following two things:
(a) The user registers with his email and a password (The email is unique in
the database). I wanted to store the email in the AuthenticatedWebSession and
load the desired user data during each request of a WebPage. Would that be a
good idea?
(b) I read in the documentation about the WebRequestCycle. Would it be useful
to implement an own WebRequestCycle for the loading of the user data?
I hope to hear some opinions. Thanks in advance.
Andre
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
