Client vs Server State Saving

[Julián García <jg...@unionsoluciones.com.co>]

Hi all,

I have been trying to introduce ajax anywhere in my project (using 
myfaces). However, it looks like it requires you to use 
STATE_SAVING_METHOD = server. Is this common to all ajax applications?

On the other hand, what are the consequences of using server state 
saving, I am a little bit concerned about this.  Does this imply an 
impact in network? Are there any componenents that do not work with 
server-side state saving?

Thanks for any comments....

Julian

Re: Client vs Server State Saving

[Werner Punz <we...@gmx.at>]

Julián García wrote:
> What is the back button issue, is there any available info on this?
> 
> Thanks
> 
Back button issue basically means that due to the mix of post and
server side storing, the back button is basically rendered "useless".
Back should mean the app has to go back into the state before the last
link or whatever triggered a page/state change.

This works to some degree with client side state saving with server side
not, because the server does not know that a back was issued
and does not restore the old state, while client side
saving should restore the old values saved into the form.

Re: Client vs Server State Saving

[Julián García <jg...@unionsoluciones.com.co>]

What is the back button issue, is there any available info on this?

Thanks

Werner Punz wrote:
> Julián García wrote:
> 
>>Hi all,
>>
>>I have been trying to introduce ajax anywhere in my project (using
>>myfaces). However, it looks like it requires you to use
>>STATE_SAVING_METHOD = server. Is this common to all ajax applications?
>>
>>On the other hand, what are the consequences of using server state
>>saving, I am a little bit concerned about this.  Does this imply an
>>impact in network? Are there any componenents that do not work with
>>server-side state saving?
>>
>>Thanks for any comments....
>>
>>Julian
>>
> 
> the components are fine, you have to have in mind that
> the data just is serialized into the session and removed
> from there, the components do not care where the data is serialized to.
> The biggest problem you might run into is the back button issue.
> 
> 
> Werner
> 

Re: Client vs Server State Saving

[Werner Punz <we...@gmx.at>]

Julián García wrote:
> Hi all,
> 
> I have been trying to introduce ajax anywhere in my project (using
> myfaces). However, it looks like it requires you to use
> STATE_SAVING_METHOD = server. Is this common to all ajax applications?
> 
> On the other hand, what are the consequences of using server state
> saving, I am a little bit concerned about this.  Does this imply an
> impact in network? Are there any componenents that do not work with
> server-side state saving?
> 
> Thanks for any comments....
> 
> Julian
> 
the components are fine, you have to have in mind that
the data just is serialized into the session and removed
from there, the components do not care where the data is serialized to.
The biggest problem you might run into is the back button issue.


Werner