> Maybe another solution would be to simply deactivate caching and use a
> PersistenceManager layer cache for clustering setups. For example by > using Hibernate's cache and clustering support and completely > deactivate the ItemStateManager's caches. I don't know what this would > do to performance though... Don't think I'd advocate that kind of approach either. Stefan mentions that the replication of application state is far more complicated than just synchronising the caches (all of them). I don't have enough knowledge of the code to disagree but when the development team is ready to start considering clustering (whenever that may be) then my vote would be to make the cache (a recourse similar to the PM) pluggable. In the meantime I'm off to try and get my head around the rest of the code ;) Simon PS Don't forget its almost Spring time (ioc)....;) -----Original Message----- From: Edgar Poce [mailto:[EMAIL PROTECTED] Sent: 04 April 2005 18:06 To: [email protected] Subject: Re: cluster and cache question - Bayesian Filter detected spam Hi serge Serge Huber wrote: > Maybe another solution would be to simply deactivate caching and use a > PersistenceManager layer cache for clustering setups. For example by > using Hibernate's cache and clustering support and completely > deactivate the ItemStateManager's caches. I don't know what this would > do to performance though... While I agree with most of yours and simon's opinions, I think that deactivating caching in the statemanagers is not an option. That would break well defined responsabilities in too many core components. regards edgar This email contains proprietary information, some or all of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this email, please notify the author by replying to this email. If you are not the intended recipient you may not use, disclose, distribute, copy, print or rely on this email. Email transmission cannot be guaranteed to be secure or error free, as information may be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. This email and any files attached to it have been checked with virus detection software before transmission. You should nonetheless carry out your own virus check before opening any attachment. GOSS Interactive Ltd accepts no liability for any loss or damage that may be caused by software viruses. GOSS - Ranked 4th in the Deloitte Technology Fast 50 Awards 2004 and 88th in the Deloitte Technology Fast 500 EMEA.
