Hi, Coming back to the cache discussion. I would like to support this proposal by Dave/Florian and think we can also delete Methods on Session class like cancel() and save() which are currently not implemented.
+1 for this: > - All write operations provided by CmisObject should automatically do an > object > refresh after the update. That guarantees that the object is always > consistent. > The cost for this consistency is an additional call to the repository. > - Is some cases you don't need or want this addition cost. Lets say you just > want to update a bunch of objects but you don't work with them afterwards. > That's what the operations provided by Session are good for. They just do > that and nothing else. About the transient support we can design this as an optional add on with additional interfaces and additional implementations. With a clear separation the API become easier to use. Regards, Stephan
