History expiration limit scenarios
You configure the expiration limit by setting the value of the property keymanager.lru.size to an integer in the StateManagerService.
You can specify by which circumstances the render parameters of a page are stored or discarded:
1Each time that the user selects a different page, the render parameters of the portlets on the previously selected page can be discarded.
A positive integerSpecify the required number of pages. The render parameters of a given page can be discarded after the user has visited that number of other pages.
0Render parameters are always stored in the portal session memory and never discarded.
Do not specify a value below zero ( 0 ). Negative values are considered to be not valid.
Example scenario: Configuring a limit to the history of viewed pages
- The configuration setting is set to a history value of 2.
- The portal pages A, B, and C contain separate instances of the standard portlet API compliant document viewer portlet A1, B1, and C1. Each of the portlets display page 1 of the same document on each page A, B, and C. Default.for the portlet.
- The user selects portal page A and navigates to page 2 of the document in portlet A1.
- The user selects portal page B and navigates to page 3 of the document in portlet B1.
- The user selects portal page C and navigates to page 4 of the document in portlet C1.
- The user selects portal page B. Portlet B1 displays page 3 of the document as before.
- The user selects portal page C. Portlet C1 displays page 4 of the document as before.
- The user selects portal page A. Portlet A1 displays page 1 of the document because this is the default state for this portlet. The previous state has been discarded because it is back in the view history by 3 pages already, and thereby exceeds the configuration setting of only 2 pages.
- The user selects page C. Portlet C1 still displays page 4 as before as it is within the configured history value of two stored pages.
Browser behavior and scenarios