A question then is: What's the different behavior then with the back-button in the browser, different for propagation "none" versus "end". Seam supposedly (and as far as I have seen) is quite gracious about using the browser back button and then continuing to work from there. But isn't that ability a bit dependent on the conversation still being around, either active or at least inactive? So then if "none" has been used and the conversation is "gone", what will happen when the user uses the back button and goes to where that conversation has been? A new conversation, if configured right? Where is the conversation stored anyway? Is that part of what we decide in web.xml to be javax.faces.STATE_SAVING_METHOD client or server? Or is the conversation independent of that? Always on server? If on client, then does "client" store one conversation, or all inactive conversations as well? Maximum size in theory and in some real use sizes? As summary question: Will the back button work better if we use "none", at higher cost of storing? Will the back button work less well if we use "end", but give benefit of less state being shuffled to client and back? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028487#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...