On Fri, Jul 6, 2012 at 12:07 PM, Carsten Ziegeler <[email protected]> wrote: > ...I think we can either choose one of two ways: > - persist each change immediately; this was my initial idea. But > obviously this has performance and consistency drawbacks. Consistency > could be sovled with JTA transactions. > - keep changes in a transient space and have an explicit save call > > The second option seems more natural and as long as only one resource > provider is affected by the changes, everything is fine....
IMO, having only one writable resource provider should be the standard case, the one that we design for. Multiple writable resource providers might be cool in theory, but supporting it 100% is a lot of work, we might keep that for later. -Bertrand
