jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Danner, Russ" <Dann...@csps.com>
Subject RE: node caching
Date Sat, 17 Mar 2007 16:58:10 GMT

what are the cons of that approach?  Is there a background thread actually persisting the
changes?  What happens when the machnine fails for some reason? From the javadoc it looks
like a bad option... like a toy that one would use for testing (it says the class should only
be used for testing.)  Maybe it could be adapted to act as a cache.

-R



-----Original Message-----
From: Harry Moore [mailto:harry.moore@eyestreet.com]
Sent: Fri 3/16/2007 10:45 PM
To: users@jackrabbit.apache.org
Subject: Re: node caching
 
Looks like InMemPersistenceManager persistance is the way to go.

Harry Moore wrote:
> Is there a way to flag a node, set of nodes or some other segment of a 
> jackrabbit repository for high-speed access? That is, cache frequently 
> accessed nodes in memory (with write-through update) so they can be 
> accesses very quickly.
>
> Thanks,
>

-- 
Harry Moore
Eye Street Software
Office: 888-252-2085 ext. 3013
Cell: 617-429-3666



Mime
  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message