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...
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.
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.
Ok, I see now.
Thank you guys for explaining it to me. You're great!