[JBoss-dev] [JBossCache] - CacheLoader: exists() before get() inefficient - solution?

2005-03-28 Thread AntonyBlakey
I have a CacheLoader that I am using to allow a TreeCache to act as the primary interface to a DAV/JDBC data model. Each access to the backend can be quite expensive. I note that a CacheLoader.get() is always preceeded by a CacheLoader.exists(), which seems redundant to me and has the

[JBoss-dev] [JBossCache] - Opinion: TreeCache/CacheLoader isomorphism

2005-03-28 Thread AntonyBlakey
I understand that the desire to form delegating cache networks has led to TreeCache and CacheLoader having the same interface, but IMHO that interface should be split into two so that the delegation/CacheLoader interface doesn't contain non-canonical methods such as get(Fqn, Object),

[JBoss-dev] [JBossCache] - CacheLoader.exists(Fqn) being repeatedly called with the sam

2005-03-27 Thread AntonyBlakey
I have implemented a CacheLoader and I noticed that the exists(Fqn) method is being called in respose to TreeCache.get() with the same Fqn multiple times. This is happening as it walks the Fqn down to my node. This seems incorrect - I would expect the Fqn passed to exists() to start at the root