sure that sounds good, we can merge interfaces as needed,
marc
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Bordet, Simone
> Sent: Wednesday, August 23, 2000 9:47 AM
> To: 'jBoss Developer'
> Subject: RE: [jBoss-Dev] Cache structures
>
>
> Hey people,
>
> while still in vacation, I managed to get a phone line and answer you
> (mountains in Italy are not so plenty of phone lines working well :)
>
> So, my status is this:
>
> I have a full working stateful cache, with overager and resizer, changed
> also the EJX gui to reflect the new cache structure and setting
> options. It
> does run the TestBeans.jar and many other tests I've written.
> I'm finishing these days the entity cache, but given the experience on the
> stateful I think I'll be done in few days (but please leave me
> some vacation
> left until monday :)
>
> Marc, I'm reading the 500+ email I've lost in these days (so maybe I don't
> have the full picture yet), but with Rickard we agreed that there
> will be a
> class for entity and stateful cache, and an interface for the
> algorithm that
> the cache will use; the class is delegating the real cache work to an
> implementation of this interface. Is this acceptable to you ? This will
> leave pluggable the cache performance, algorithm and settings (I made the
> suitable changes also to the EJX GUI and to jboss.xml to support this). Up
> to now there is only one implementation of the CachePolicy interface: the
> one for the LRU algorithm, but there are open possibility to other
> algorithms as well.
>
> If you can answer in minutes OK, otherwise I will read your answer(s) on
> monday.
>
> Bye
>
> Simon
>
> > -----Original Message-----
> > From: Rickard �berg [mailto:[EMAIL PROTECTED]]
> > Sent: mercoled� 23 agosto 2000 8:31
> > To: jBoss Developer
> > Subject: Re: [jBoss-Dev] Cache structures
> >
> >
> > Hi!
> >
> > marc fleury wrote:
> > > Whereas I insist that "ease of use" is the main goal (i.e.
> > that in 80% cases
> > > developers are going to create and call methods to bench
> > complex PKs and
> > > most will not override the hash equals correctly or
> > effectively) and in that
> > > case we are sitting much prettier, I also believe it is not
> > an absolute
> > > priority to introduce some complexity in the cache at this point.
> > >
> > > I will make the cache structures pluggable so we can use
> > either the base
> > > cache or the advanced one based on jboss.xml. That is what
> > the architecture
> > > is there for and only the client needs to be a bit smarter
> > but that is minor
> > > changes. The EntityInstanceCache is also imho a missing
> > piece of the puzzle
> > > and I will add that but the implementation of the actual
> > cache will be the
> > > old one. Use the new one as needed, pluggable.
> > >
> > > How does this sound?
> >
> > Well, since Simone is working on a more advanced cache for both entity
> > and stateful wouldn't it be double work?
> >
> > Simone, what's your status?
> >
> > /Rickard
> >
> > --
> > Rickard �berg
> >
> > Email: [EMAIL PROTECTED]
> > http://www.telkel.com
> > http://www.jboss.org
> > http://www.dreambean.com
> >
>
>
