so I don't think a load balancing approach prevents flow from working. The only issue open is the continuations tree which is stored in a global component and not in the session. IIUC this is a problem in clustered environments, isn't it? (IIRC there was a discussion some weeks ago, Thorsten what do you think?)
Me?
...same as for sessions - we only need to come back to the same JVM.
Basically we have some overlap with sessions here. From the load balancing POV flow is not very different to sessions. So we can reuse the same concepts.
If your web app creates a session and you use the outlined concept for load balancing you should be fine with flow as well. Problem only kicks in if you use flow without sessions.
But this could also be solved easily as Pier already suggested by adding some kind of prefix to the continuation id that identifies the JVM. -- Torsten
