Are you saying that because HTTP Session will contain the last-displayed-page, a single back button after failover should have worked because the second server would have persisted that one page to its own disk?
On Thu, Oct 22, 2009 at 4:49 PM, Matej Knopp <matej.kn...@gmail.com> wrote: > Yes. But wicket tries to store the page being sent across cluster > during replication when the session is deserialized on target node. > > -Matej > > On Thu, Oct 22, 2009 at 11:46 PM, Randy S. <randypo...@gmail.com> wrote: > > Isn't this caused by the storage of past pages in files on disk rather > than > > in HTTP Session? This is in the default ISessionStore implementation (see > > SecondLevelCacheSessionStore, DiskPageStore). >
