Hello Simon, > There cannot be two simultaneous copies of the "request" or "session" scopes, > and >neither can there be (yet) simultaneous copies of an orchestra-created > scope.
I thought a user can have more simultaneous request going on; If we have on the timeline 4 points: A,B,C,D, an action is made on a request beanX (from time A to D) and the same user make an action on a request beanX (from time B to C) - from time B to C the user would have 2 simultaneous request (2 instance of beanX). Right? I think that the orchestra conversation (or conversationContext?) can exist simultaneously; the problem is I cant switch between conversation; I can do it manually; conversationContext=1 The user enters a 3 step (step1, step2, step3) conversation and arrives to step2. Then he wants to do the exactly same thing (with other input for example): conversationContext=2 (i set the id manually in the browser url paramater) The user enters the conversation and arrives to step3. Now he is going back to conversationContext=1. conversationContext=1 (i set the id manually in the browser url paramater) Perfect, I am where I want (step 2) with the data I want. I can go to step 3. Now back to converastionContext2. conversationContext=2 (i set the id manually in the browser url paramater) Perfect, I am where I want (step 3) with the data I want. etc >name will look through all the known scopes and return the bean wherever it is - request, >session, or otherwise. I would like the beanX (or a group of beans) to be in conversationContext1 and conversationContext2; as many instances of those beans as many conversations; > Is that the kind of scenario you have to deal with? Or is it something else? My scenario: the user is browsing through data. The data is devided into tabs. Each tab is a sequence of steps-reports (conversation). > The other option is to create a whole new "conversation context", where all > of the >conversations are new. There is no easy way to communicate between > contexts though... Yes, I think this is what I was trying to say. I thought conversation can be used if one user can do a number of steps (like the orchestra computer configuration example) but in few instances (for example we are in a PC shop and a customer is telling us the PC configuration, but in the middle he made a break to go to the toilet, there is a new customer waiting so while the other guy is in the toilet we can start a new PC configuration and switch to the previous when the customer is back from the toilet). Sorry if I m not clear or I going the wrong way. mac
