I think some use cases would be useful here, to assess how much of a problem / not-a-problem this is, and whether this is an area that is so application-specific that a pre-specified "framework" is inappropriate.
On the "no" side it's worth noting that building higher-level abstractions on a JCR-compliant repository will be a lot easier than on top of an RDBMS, thanks to the mechanisms that Julien mentions. But on the "yes" side, I would certainly prefer to deal with higher-level objects, and I would also appreciate an ecosystem of pre-written ones to help me. Does this imply that a framework is needed? I started to talk about this on jackrabbit-dev previously ( http://www.mail-archive.com/[email protected]/msg00639.html ) where I talked about a "TableAtom" (in JCR parlance this would be a TableProperty, I guess) that wrapped a Property and added a high-level API to get/set table entries in a table encoded as a string. I didn't get a lot of interest in that thread :) but I think it's a valid idea, and one that has caused me *real-life pain* in the past. So: an issue or not an issue? On 4/16/05, Julien Viet <[EMAIL PROTECTED]> wrote: > invalidate the cache : > > - time based invalidation, you say that an entry is valid for 1 minute > for instance > - notification, you can use JCR observations mechanism to remove entries > from the cache > > cheers > > Daniel Dekany wrote: > > >I suppose most applications want to work with objects like mycms.User, > >mycms.PageTemplate, myapp.Book, etc., rather than directly with the tree > >of items that JCR shows. I don't see what's the intended way of doing > >this. With a concrete example: I would like to store page templates in > >the repository, which are complex and frequently used objects, so they > >shouldn't be recreated from a binary property (or from string string > >property, whatever) every time they are read from the repository (that > >is, for each page hits). I could use cache in front of JCR that caches > >the template objects, but how to ensue that the cache is in sync with > >the repository? Of course no hazards and unpredictable delays are > >allowed after the repository was modified. > > > >What's the planned way of doing things like this? > > > >(I know this is not a Jackrabbit but a JCR question and I apologize for > >that, but I didn't found a more suitable public list.) > > > > > > > > -- > Julien Viet > JBoss Portal Lead Developer > > -- Cheers, Ben
