Shouldn't the change token solve that? How do we deal with the change token for other objects that are in the local cache? Ignore? Check on each access? Configurable?
Jens -----Original Message----- From: Florian Müller [mailto:[email protected]] Sent: Montag, 15. November 2010 21:17 To: [email protected] Subject: getObjectByPath cache problem Hi all, I had another look at [1]. Unfortunately, it's an unsolvable problem. I can think of three ways to cope with it: 1. We leave it like it is, although it is very, very confusing when you run into this situation. 2. We don't cache by path. How would that affect applications? 3. When getObjectByPath is called we fetch the object id from the repository and then get the object from the cache. In the worst case, we would have to hit the repository twice. Any opinions? - Florian [1] https://issues.apache.org/jira/browse/CMIS-260
