Sorry I mistyped: default is REDIRECT_TO_BUFFER. On Thu, Mar 28, 2013 at 2:36 PM, Dan Retzlaff <[email protected]> wrote:
> Hi Marios, > > This behavior is determined by IDataStore interface. DiskDataStore is used > by default, so only the most recent page is kept in the session (and > available for failover). It puts page history into a directory specified in > "javax.servlet.context.tempdir" servlet attribute (under "work" directory > in Tomcat). If you want more page history available on failover, specify a > IPageManagerProvider in your Application#init() that constructs > HttpSessionDataStore instead. Note HttpSessionDataStore's > IDataStoreEvictionStrategy dependency which keeps session usage under > control. > > If Wicket clustering is new to you, also note that Wicket > uses RenderStrategy.REDIRECT_TO_RENDER by default. See javadoc for details, > but in short: you should configure your load balancer for sticky sessions. > > Dan > > On Thu, Mar 28, 2013 at 2:17 PM, Marios Skounakis <[email protected]>wrote: > >> Hi all, >> >> I >> 'm planning to setup a terracotta tomcat cluster. The wicket site claims >> that "all Wicket applications will work on a cluster automatically and >> without additional work >> " >> . >> >> I understand that basically since session state is kept in serializable >> objects within the http session, it mostly works. >> >> But is it true that NO changes are needed? Do I need to change any >> settings? What does the page store do once it has to push a page from >> memory to disk? >> >> >> T >> hanks in advance >> Marios >> > >
