Right, for a clustered environment (which Roller should support - even
if file uploads and such don't work so well) - we'd need to use JBoss
TreeCache or OSCache.  I've used OSCache (with JGroups) with good
success - but we did have to modify some files for Hibernate 3.

http://opensymphony.com/oscache/wiki/Hibernate.html

Matt

On 1/11/06, Jeff Blattman <[EMAIL PROTECTED]> wrote:
> stupid newbie comment ... does roller support multi instances? if it
> did, l2 cache becomes problematic unless it's a super-smart
> implementation that sync's itself across instances.
>
> Allen Gilliland wrote:
>
> >yes? no? anybody?
> >
> >i'd like to commit a *very* modest version of a hibernate L2 cache which 
> >would use ehcache and only apply to a few objects ... RollerPropertyData, 
> >WebsiteData, and UserData.
> >
> >-- Allen
> >
> >
> >On Mon, 2006-01-09 at 18:59, Allen Gilliland wrote:
> >
> >
> >>One of the things that we currently do not take advantage of is object
> >>level caching.  Hibernate makes it pretty easy to add an L2 cache on a
> >>class by class basis, so I'd like to start by adding an L2 cache for a
> >>handful of classes like ... RollerPropertyData, WebsiteData, and
> >>UserData.  All three of those classes are highly used and seldomly
> >>changed, so they are ideal for caching.
> >>
> >>We can play with a variety of possible cache implementations, but
> >>EhCache is the default and seems easiest to use at this point.
> >>
> >>Would anyone object to this?
> >>
> >>-- Allen
> >>
> >>
> >>
> >>
> >
> >
> >
>
>

Reply via email to