session-scoped cache is faster then the other memory levels but it contains only the pages used to serve the last request. Wicket allows us to set the maximum amount of memory allowed for the 48 application-scoped stateful pages, but sometimes we might want to use an “old school” stateless page that doesn’t keep memory of its state in the user session. For example consider the public area of a site or a login page: could be a very large instance, hence serialization would become very expensive in terms of time and memory. 2. We simply may not be able to use a serializable object as model object. In paragraphs 1.4 and

session-scoped cache is faster then the other memory levels but it contains only the pages used to serve the last request. Wicket allows us to set the maximum amount of memory allowed for the 47 application-scoped stateful pages, but sometimes we might want to use an “old school” stateless page that doesn’t keep memory of its state in the user session. For example consider the public area of a site or a login page: a very large instance, hence serialization would become very 91 expensive in terms of time and memory. 2. We simply may not be able to use a serializable object as model object. In paragraphs 1.4 and

stateful pages, but sometimes we might want to use an “old school” stateless page that doesn’t keep memory of its state in the user session. For example consider the public area of a site or a login page: could be a very large instance, hence serialization would become very expensive in terms of time and memory. 2. We simply may not be able to use a serializable object as model object. In paragraphs 1.4 and tells the client which bytes are going to be send. If you want the resource not to be load into memory apply readBuffered(false) - this way the stream is written directly to the response. (org.apache

stateful pages, but sometimes we might want to use an “old school” stateless page that doesn’t keep memory of its state in the user session. For example consider the public area of a site or a login page: could be a very large instance, hence serialization would become very expensive in terms of time and memory. 2. We simply may not be able to use a serializable object as model object. In paragraphs 1.4 and tells the client which bytes are going to be send. If you want the resource not to be load into memory apply readBuffered(false) - this way the stream is written directly to the response. (org.apache