-
1. Re: Conversation scope questions
pmuir Nov 2, 2007 6:48 AM (in response to johnfish)No. The conversation lifespan is limited to the session length, and can timeout before that if there is no user activity for a user-defined period of time (default 10 mins).
The session is unaffected and behaves as though you were using servlets. -
2. Re: Conversation scope questions
johnfish Nov 2, 2007 6:53 AM (in response to johnfish)Yeah but then whats the difference between session scope and conversation scope?
-
3. Re: Conversation scope questions
pmuir Nov 2, 2007 6:56 AM (in response to johnfish)You can have multiple conversations per session (maximum of one active/foreground conversation per tab, unlimited inactive conversations).
-
4. Re: Conversation scope questions
johnfish Nov 2, 2007 6:59 AM (in response to johnfish)Ok. Thats what I meant before. My question is how does the framework know about browser tabs? Since it lies on the server it only sees incoming http requests. Thx
-
5. Re: Conversation scope questions
pmuir Nov 2, 2007 7:01 AM (in response to johnfish)Ok. It uses a request parameter (get or post dependent on whether its a link or a form).
-
6. Re: Conversation scope questions
johnfish Nov 2, 2007 7:05 AM (in response to johnfish)But how is this request parameter used to distinguish between tabs?
-
7. Re: Conversation scope questions
pmuir Nov 2, 2007 7:20 AM (in response to johnfish)The conversation is tied to the request parameter, not the tab.
-
8. Re: Conversation scope questions
johnfish Nov 2, 2007 7:28 AM (in response to johnfish)I dont understand. The framework must have a way to distinguish between browser tabs. You mentioned that a request param is set. Where is this set? What does it contain? And how is this useful to distinguish between browser tabs? What happens in the session level if a different conversation is opened?
-
9. Re: Conversation scope questions
pmuir Nov 2, 2007 7:37 AM (in response to johnfish)"JohnFish" wrote:
I dont understand. The framework must have a way to distinguish between browser tabs.
Why? The only way that conversations can move between tabs is by right clicking on a link which propagates the conversation via GET and choosing open in a new tab.You mentioned that a request param is set. Where is this set?
It's added to forms (well, to the page context) and to s:link/s:button automatically. You can manually add it as well.What does it contain?
It contains the conversation identifier.And how is this useful to distinguish between browser tabs?
See above -
10. Re: Conversation scope questions
johnfish Nov 2, 2007 7:42 AM (in response to johnfish)"pete.muir@jboss.org" wrote:
"JohnFish" wrote:
I dont understand. The framework must have a way to distinguish between browser tabs.
Why? The only way that conversations can move between tabs is by right clicking on a link which propagates the conversation via GET and choosing open in a new tab.
Ok. That what messed up my thinking. I assumed conversations cannot move between tabs. I can see now how this is done. Cheers"pete.muir@jboss.org" wrote:
What happens in the session level if a different conversation is opened?
Another ConversationEntry is added to the ConversationEntry map.
You're really starting to get deep into how the framework is implemented here - I suggest getting a copy of the source code and checking this out for yourself.
I didnt know the source code is available. I ll definitely have a look -
11. Re: Conversation scope questions
pmuir Nov 2, 2007 7:44 AM (in response to johnfish)Its all in every download (its all LGPL)