Alexey Maslov schrieb: > We had a working solution that provided convenient > conversation support. It had some threading issues so > we delayed it until the next Rumba release. I think > that multi-page conversations are usually not a > central part of the application and it is better to > optimize cases used the most. > Actually it is not only multi page, often pages can conveniently use this pattern on single pages. The use case most often is constant page refreshes (or virtual page refreshes), which conicidently comes hand in hand with ajax and jsf events, every time something like this happens a new session is opened and the objects cannot be recycled or have to be rebound.
With a multi session in conversation filter you load the objects and have them available as persistable as long as you stay in the page, no matter how long it is no matter which events or ajax requests are triggered. The other case is a typical crud case where you basically can pass the affected objects directly instead of having to reload them via an id and have the persistence layer itself keeping track of which objects to keep in ram or which can be dumped until the next access. (session.flush situation)
