see:
/**
* Creates a new [EMAIL PROTECTED] DiskPageStore} instance.
*
* [EMAIL PROTECTED] maxSizePerPagemap
* the maximum size of pagemap file (in bytes)
* [EMAIL PROTECTED] maxSizePerSession
* the maximum size of session (in bytes)
* [EMAIL PROTECTED] fileChannelPoolCapacity
* the maximum number of concurrently opened files (higher number improves
* performance under heavy load).
*
*/
*public* DiskPageStore(*int* maxSizePerPagemap, *int* maxSizePerSession, *
int* fileChannelPoolCapacity)
{
*this*(*getDefaultFileStoreFolder*(), maxSizePerPagemap, maxSizePerSession,
fileChannelPoolCapacity);
}
johan
On Feb 5, 2008 9:43 AM, oliverw <[EMAIL PROTECTED]> wrote:
>
> As far as I have understood the workings, Wicket maintains one PageMap per
> Browser Windows in the Session Store and a number of Page Versions per
> PageMap for every architectural change of said page. The current version
> of
> the page resides in memory while oder versions will be serialized to disk
> into a temp file.
>
> If that's correct, I'm wondering how many versions of the page will Wicket
> maintain? Is there a fixed amount? Will there be an unlimited amount of
> versions until the server runs out of temp space? Could someone lighten me
> up? :)
>
> --
> View this message in context:
> http://www.nabble.com/How-many-page-versions-will-exist--tp15285630p15285630.html
> Sent from the Wicket - User mailing list archive at
> Nabble.com<http://nabble.com/>
> .
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
