4 Replies Latest reply on Jun 3, 2009 1:23 AM by phantasmo

    A general question on conversations

    phantasmo

      I am very new to Seam, so I just have a broad question here. I have troubles understanding conversations. From what I could gather reading the Seam tutorial, a conversation is tied to a browser tab, but the booking example then confused me, because it is entirely possible to pick a hotel (starting a new conversation), fill out the booking data, clone the tab and confirm the booking from this new tab. My dilemma here is, how is it possible to confirm the booking from the new tab, if all the booking data resides in the conversation which is tied to the original tab? Also, the nested conversations booking example claims that if you clone the tab in the new windows, that new windows would participate in the same conversation as the original... Is this correct?


      Are tabs and windows handled differently, conversation-wise?
      Any bit of insight would be greatly appreciated.


      Thanks you very much for your time.

        • 1. Re: A general question on conversations
          phantasmo

          This is hopefully a no-brainer for anyone who's familiar with the booking example.


          Sorry for the bump so soon, but there's so much traffic here that a thread sinks very quickly.


          Thanks for the patience...

          • 2. Re: A general question on conversations
            mwohlf

            afaik conversations are identified by the cid parameter in the url and are stored in the http session context on the server side, so it doesn't matter how many tabs you open in the browser as long as the cid is correct and you stay in the same session.

            • 3. Re: A general question on conversations
              nickarls

              A conversation is a token (conversation id) passed along in some way (i.e request parameter or JSF view) that separates one set of instances in a instance store (i.e. the HTTP session) from another in the same store.


              It's not actually tied to browser tabs. It's just that usually browser tabs share the same session and without some sort of conversation ID, they will share the same session which causes state mixing. Sort of.

              • 4. Re: A general question on conversations
                phantasmo

                Ok, I see now.
                Thank you guys for explaining it to me. You're great!