myfaces-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yee CN <ye...@streamyx.com>
Subject RE: Session Scope Bean does NOT require serialization. Myfaces bug?
Date Mon, 19 Dec 2005 13:31:36 GMT
My understanding is that with R1.1.1 the session scoped beans are not
serialized (thus Myfaces cannot be used in clustered deployments with shared
sessions between containers). Serialization of backing beans to session is
only added in the current build - and thus my questions regarding its
performance.

Please correct me if I am wrong. 

Regards,
Yee 

-----Original Message-----
From: Aleksei Valikov [mailto:valikov@disy.net] 
Sent: Monday, 19 December 2005 6:15 PM
To: MyFaces Discussion
Subject: Re: Session Scope Bean does NOT require serialization. Myfaces bug?

Hi.

> It was a request bean, set to session scope to test out the new build.
> Actually only a few items in the bean was meant to be in the saveState,
> saving the whole bean was only a lazy way to get everything working before
> determining which objects need to be saved.
> 
> What is the performance implication of SERIALIZE_STATE_IN_SESSION=true?
> Should this be set to false unless I need to implement clustering that
> requires sharing session between containers?

I think, sessions will generally perform much better since you don't 
have marshalling/unmarshalling overhead.
Are there any good reasons to use client-side serialization at all?

Bye.
/lexi


Mime
View raw message