Has anyone tried to create a cache better suited to
multi-user environments with regard to dirty data ?
I am not a Java Virtual Proxy guru, but I would imagine that
based on the existing VirtualProxy code in OJB one would be able to
create a cache entry that is actually a proxy, and delegates
to the shared entry in the cache as long as it is read from
(I mean as long as only the getters are invoked).
Then when a setter is invoked, it instantly creates a "clone"
of the cached object, and uses that instead for all further invocations,
effectively isolating the "dirty" object from the cache.
The persistence broker would also recognise such a proxied object,
so if it is committed (stored) it could erase or refresh the shared
copy in the cache, keeping it up to date without much
programmer intervention.
Would this suggestion work, or are there obvious shortcomings ?
Cheers,
Theo Niemeijer
> -----Oorspronkelijk bericht-----
> Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Verzonden: dinsdag 3 juni 2003 12:00
> Aan: OJB Users List
> Onderwerp: Re: Cache question
>
> >
> >>And if you don't want to handle many OL exception you can set
> >>refresh="true" for all persistent classes.
> >
> >
> > Which means there will be no caching at all.
>
> There is still caching, but is ignored.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
