Avoid page serialization

2008-07-10 Thread Daniele Dellafiore
I am wondering if page serialization in wicket is always necessary. I
have read this:

Wicket keeps its tree of components in the session. In a clustered
environment, session data needs to be replicated across the cluster.
This is done by serializing objects in a cluster-node's session and
deserializing them on another cluster-node's session

here: http://cwiki.apache.org/WICKET/spring.html

So I have asked myself: what if I do not have a clustered environment?
Is serialization really needed anyway?

-- 
Daniele Dellafiore
http://blog.ildella.net/

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



Re: Avoid page serialization

2008-07-10 Thread Johan Compagner
yes with the default pagestore of 1.3+ this is needed
We serialize pages to disk.

On Thu, Jul 10, 2008 at 10:37 AM, Daniele Dellafiore [EMAIL PROTECTED]
wrote:

 I am wondering if page serialization in wicket is always necessary. I
 have read this:

 Wicket keeps its tree of components in the session. In a clustered
 environment, session data needs to be replicated across the cluster.
 This is done by serializing objects in a cluster-node's session and
 deserializing them on another cluster-node's session

 here: http://cwiki.apache.org/WICKET/spring.html

 So I have asked myself: what if I do not have a clustered environment?
 Is serialization really needed anyway?

 --
 Daniele Dellafiore
 http://blog.ildella.net/

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




Re: Avoid page serialization

2008-07-10 Thread Matej Knopp
It is necessary as wicket uses serialization to make snapshot of page
state to be able to revert it back on back button.

-Matej

On Thu, Jul 10, 2008 at 10:37 AM, Daniele Dellafiore [EMAIL PROTECTED] wrote:
 I am wondering if page serialization in wicket is always necessary. I
 have read this:

 Wicket keeps its tree of components in the session. In a clustered
 environment, session data needs to be replicated across the cluster.
 This is done by serializing objects in a cluster-node's session and
 deserializing them on another cluster-node's session

 here: http://cwiki.apache.org/WICKET/spring.html

 So I have asked myself: what if I do not have a clustered environment?
 Is serialization really needed anyway?

 --
 Daniele Dellafiore
 http://blog.ildella.net/

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



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