First of all don't worry that much about the session usage, in 1.3 we only store 1 page per pagemap in the session, the rest is stored to disk
> 1. So, Can I manually interval the session and remove the objects stored > in the session? > What kind of objects? If you store the object in the Wicket session object, then they are in the session And what is that interval? A scheduler? You shouldn't touch sessions when the request isn't happening. 2. Can I manually view all the objects stored in a session? > We have some debug tools like page inspector, See examples for that. 3. If the size of the page map is set to 5 for example does that mean that > these 5 pages and associated components, models will be stored in the > session and other will be removed from the session? > In wicket 1.2 yes. in wicket 1.3 that size isn't being used anymore. Only the active page is there. 4. The default first cache level is the file system. So what will have if I > sit a limit of the file system size? Will it override it? Will the lost > components be created again instead of being retrieved from the cache? > Currently you can control what the window is that a session gets. i think by default it is 10MB or something like that. So 1 session will not grow out of control. If of course you have a full disk then sessions can't be saved and those are lost. But do remember that those pages on disk are pretty much only there for the back button' If the users don't use the backbutton then the disk is not used for reading the pages back in. 5. What are the best practices of handling a session? > Just let wicket handle it. Don't store objects directly in the http session your self (use the wicket session object for that) Also use detachable models for you data. Don't keep the whole database in memory between request. That will greatly explode your pages. johan >
