These sessions are very similar to ASP.NET sessions and objects can be stored in the session on various string keys. But there are some differences from the ASP.NET sessions.
The ASP.NET sessions time out after a given period of inactivity, and the session gets deleted. Jaxcent sessions also time out and get deleted, but the time-out period does not start as long as the browser stays on a Jaxcent page containing the session. Every time the browser leaves a Jaxcent page containing the session, the session time-out starts. But if the browser visits another Jaxcent page again, the time-out is reset again. (Of course, this behavior can be over-ridden by programmatically deleting the session as necessary, for security or other reasons. A separate thread should be started for this that waits N minutes and then deletes the thread if the user is on the same page - see Multiple threads in Jaxcent pages.)
Because the Jaxcent time-out doesn't start until the user has definitely left the application, the Jaxcent time-out period has a smaller default, of 5 minutes.
Jaxcent sessions are not enabled by default, and the programmer must indicate that a session is required for a given page, by using the "use-session" parameter when wiring up the page for Jaxcent.Use-session can be enabled during the Jaxcent hook-up of HTML or ASPX pages.
OnPageLoadevent has fired. All event handlers for button clicks etc fire after that, so it's not a problem in typical programming - excpept when initializing data from constructors. In constructors, because the page is not loaded yet, the session will be
See Automatic Handling of Data in Jaxcent via Sessions for details on the automatic data collection.