Terracotta Discussion Forums (LEGACY READ-ONLY ARCHIVE)

I searched all around about Wicket + TC session clustering but everything I've found seems to be related to the old DSO session clustering.

My question is quite simple actually...Should I use HttpSessionStore or SecondLevelCacheSessionStore (the default)?

As far as I know, SLCSS delegates page resolution to DiskPageStore, which (de)serializes pages from/to the disk in order to avoid excessive RAM consumption.

I think that DiskPageStore is meaningless for failover unless the files are written on some sort of NFS, which is not my case.

If I use HttpSessionStore, everything will be put directly into the HttpSession provided by the container (the Terracotta HttpSession impl). Does WebSessions work more or less like DSO, in the sense that keys are kept in memory and data is faulted to/from the TC server, keeping RAM in check?