On 12/8/06, Nebinger, David <[EMAIL PROTECTED]> wrote:
For client side state saving, no state information will be kept on the server (your session information you've stored is still safe). You normally choose this option when you have large views to deal with or you are serving many end users; in both cases you've made the determination that you're willing to sacrafice the network bandwidth in order to conserve server memory resources.
Or you use client-side if you don't want to deal with backtracking limitations, or you want to support multiple windows open at the same time in JSF 1.1, or if you want your user "sessions" to be able to transparently survive a crash/restart (assuming you don't change the serialization in the code).
