Sokrates Documentation
- Sessions |
Sessions You can request a session context by calling the .getSession() method of the current request. A session holds your data between requests. The identification of this session is done by a session ID. There are 2 possibilities to store this ID:
If you select sessionid=url you must use HttpServletResponse#encodeURL(String) on every URL your servlet produces because the session ID must be crypted into the URL instead of storing the ID into a cookie. A typical URL with a session ID in the URL looks like this: http://www.harddiskcafe.de/taskplaner?hAction=login&ssrsessionid=IDee82a59375-3 Session manager The session manager handles storing, retrieving and deleting of outdated sessions. The session manager is pluggable so you can replace it with your own version and implement your own session management rules. The parameter sessionmanagerconfig can point to an init file (.ini) with a valid configuration; if the parameter is left empty the "Memory Session Manager" mode is used with its default values. We deliver two different, preconfigured versions in the Sokrates distribution:
<< How does it work ? <<
>> to be continued >>
|
Main
- Installation - Stopping
and Restarting - Adding New Servlets - Better Structures - How does
it work ? - Sessions - |