InfoCenter Home > 4.4.1.1.7.6: Tuning session support: Write contentsIn Session Manager, you can configure which session data is written to the database. The following options are available in Session Manager for tuning what is to be written back to the database:
The Write all setting might benefit servlet and JSP writers who change Java objects that reside as attributes in an HttpSession instance. Previously, every programmatic change in an attribute would require a setAttribute() call to make sure changes were reflected in the database in a timely manner. In most cases, the use of this setting eliminates the need for all but the initial setAttribute() call to bind the object to the session. However, the use of Write all could result in more being written back to the database than is necessary. If this situation applies to you, consider combining the use of Write all with Time-based write to boost performance overall. As always, be sure to evaluate the advantages and disadvantages for your installation. With either Write Contents setting, when a session is first created, complete session information is written to the database, including all of the objects bound to the session. In subsequent session requests, what is written to the database depends on whether a single-row or multirow schema has been set for the session database, as follows:
|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|