Re: How many page versions will exist?

2008-02-05 Thread Markus Strickler

Hi-

you might want to have a look at
Application.getPageSettings().getMaxPageVersions() and the corresponding API
docs.
This is also the place to change the number of versions.

-markus

Zitat von oliverw [EMAIL PROTECTED]:



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.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







This message was sent using IMP, the Internet Messaging Program.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



How many page versions will exist?

2008-02-05 Thread oliverw

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.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: How many page versions will exist?

2008-02-05 Thread oliverw

Thanks Markus. Unfortunately this won't compile with 1.3. I've checked the
IPageSettings interface and there's no such methods. Its method
getVersionPagesByDefault() which returns a boolean is as close as it gets.
Other suggestions? :)


Markus Strickler wrote:
 
 Hi-
 
 you might want to have a look at
 Application.getPageSettings().getMaxPageVersions() and the corresponding
 API
 docs.
 This is also the place to change the number of versions.
 
 -markus
 
 Zitat von oliverw [EMAIL PROTECTED]:
 

 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.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


 
 
 
 
 This message was sent using IMP, the Internet Messaging Program.
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/How-many-page-versions-will-exist--tp15285630p15286058.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: How many page versions will exist?

2008-02-05 Thread Martijn Dashorst
When you don't let your sessions expire or have a very long session time
out, you might run into disk space problems, though the moment you have 1TB
of disk space allocated for all your sessions, I suppose you can afford to
buy more disk space.

Martijn

On 2/5/08, 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.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-- 
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0


Re: How many page versions will exist?

2008-02-05 Thread Johan Compagner
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.comhttp://nabble.com/
 .


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




Re: How many page versions will exist?

2008-02-05 Thread oliverw

Thanks Johan. So if the the maximum number of generations or storage space is
exceeded - whichever comes first - older versions get discarded and the user
will not be able to navigate to those versions using the back button.


Johan Compagner wrote:
 
 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.comhttp://nabble.com/
 .


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


 
 

-- 
View this message in context: 
http://www.nabble.com/How-many-page-versions-will-exist--tp15285630p15286570.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: How many page versions will exist?

2008-02-05 Thread Johan Compagner
yes old pages will be overwritten by new onces

johan



On Feb 5, 2008 10:43 AM, oliverw [EMAIL PROTECTED] wrote:


 Thanks Johan. So if the the maximum number of generations or storage space
 is
 exceeded - whichever comes first - older versions get discarded and the
 user
 will not be able to navigate to those versions using the back button.


 Johan Compagner wrote:
 
  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/http://nabble.com/
  .
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 

 --
 View this message in context:
 http://www.nabble.com/How-many-page-versions-will-exist--tp15285630p15286570.html
  Sent from the Wicket - User mailing list archive at 
 Nabble.comhttp://nabble.com/
 .


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]