Hi,

I have just re-introduced caching into the OpenCMIS client API. While caching 
objects by id makes perfect sense, I'm not so sure about caching by path. 
Objects could have been deleted, recreated, moved, etc. and the path actually 
points now to a completely different object. I assume that could be a problem 
for some applications.

Should we cache by path at all? Should the path cache have an expiration date 
to minimize the impact? Any opinions?


- Florian

Reply via email to