[jboss-user] [JBoss Seam] - Re: How bad is unused conversations?

[stephen.friedrich]

Hm, I think explicit conversation ids only make sense when the application logic naturally suggests them. (Like using an article id for an article editor - it really makes no sense to edit the very same article in different conversations).

To make matters more concrete: Image a UI that shows a tabbed pane where each tab hosts a possible step of interactions.
So you want each tab to have a conversation of its own. However if you simply assign fixed conversation ids you will loose the ability to open new browser windows/tabs.

There's a lot of documentation how context demarcation technically works, but there is close to none how it it relates to interaction design.

Note that you would not have to think twice about how to implement this in a rich client: Each tab instance would simply holds its model which is "commited" at the final step of the task.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067412#4067412

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067412