but wouldn't that be a different implementation of sessionstore? i thought this would be a concrete class.
the thing about "cache" is that it's the opposite of what this is. a cache normally holds a faster often temporary copy of something. in this case, the thing that's in memory and in the session is the cached page. the session store here is actually slower storage which actually reduces speed in order to increase resource availability (memory and session space). in some sense, it's exactly the opposite of a cache. it's more like an OS paging file. maybe something more like PagePersistingSessionStore? Eelco Hillenius wrote: > >> btw, SecondLevelCacheSessionStore seems a little fuzzy to me as a name. >> it presumes someone knows what a "second level cache" is. what about >> something a little more direct like maybe FileBackedSessionStore? not >> sure >> i love that either, but it's maybe a little more obvious. > > I don't know. It doesn't have to be stored in the file system (at > least not according to the original idea) but could for instance be > stored in a database system. > > Eelco > > -- View this message in context: http://www.nabble.com/refactor-storing-pages-and-versions-tf2943670.html#a8233508 Sent from the Wicket - Dev mailing list archive at Nabble.com.
