pages. The chapter also introduces some advanced topics like Java Serialization and multi-level cache. However, to understand what you will read you are not required to be familiar with these concepts level cache to speed up this process. The first level of the cache uses a http session attribute called “wicket:persistentPageManagerData-” to store pages. The second level cache stores a page id. The following picture is an overview of these two caching levels: The session-scoped cache is faster then the other memory levels but it contains only the pages used to serve the last request

pages. The chapter also introduces some advanced topics like Java Serialization and multi-level cache. However, to understand what you will read you are not required to be familiar with these concepts levels cache to speed up this process. The first level of the cache uses a http session attribute called “wicket:persistentPageManagerData-” to store pages. The second level cache stores a page id. The following picture is an overview of these two caching levels: The session-scoped cache is faster then the other memory levels but it contains only the pages used to serve the last request

pages. The chapter also introduces some advanced topics like Java Serialization and multi-level cache. However, to understand what you will read you are not required to be familiar with these concepts of pages into a session-relative file on disk, but it uses a two- level cache to speed up the access. The first level of the cache contains all the pages involved in the current requests as we may visit a single request, for example if we have been redirected with setResponsePage. The second level cache stores the last rendered page into a session-scoped variables.  Scoped variables will be introduced

pages. The chapter also introduces some advanced topics like Java Serialization and multi-level cache. However, to understand what you will read you are not required to be familiar with these concepts of pages into a session-relative file on disk, but it uses a two- level cache to speed up the access. The first level of the cache contains all the pages involved in the current requests as we may visit a single request, for example if we have been redirected with setResponsePage. The second level cache stores the last rendered page into a session-scoped variables.  Scoped variables will be introduced