Hi all, Just for my interest, could anybody explain what would be the point of that??
As Simon said, it's basically server-side state saving with a single client-side token. But normal server-side state saving already has a token (the SESSION ID!!) that maps to the HttpSession anyway... so what's the difference?? Thanks, Daniel. -----Original Message----- From: Simon Kitching [mailto:[EMAIL PROTECTED] Sent: Wednesday, 31 January 2007 1:31 PM To: MyFaces Discussion Subject: Re: Jsf_tree_64 Yep, so in other words it's the same as server-side state saving, except that there is also a single client-side field that indicates which server-side state block it is associated with. No savings there in memory, though it may help keep things in order when people use back/forward buttons etc. Actually, normal MyFaces behaviour is to render a counter into the client when using server-side state saving for exactly this same purpose. There are some proposals around to reduce the amount of JSF state that needs to be maintained, but AFAIK all these cause changes in JSF behaviour, ie would not be compliant with the current JSF spec.
