You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user-java@ibatis.apache.org by Sergey Livanov <Se...@ukrpost.net> on 2005/02/03 08:59:25 UTC
cash question
Could you please help me figure out the cache scheme.
When I'm within one application I can use the flush method.
How should I correctly develop a cashing scheme if data is saved by one
application and displayed by another? Would it be helpful to have a
signal record that I initially read from the database and then,
if the data changed, do a forced flush?
--
regards,
Sergey mailto:Sergey.Livanov@ukrpost.net
Re: cash question
Posted by Clinton Begin <cl...@gmail.com>.
Sounds like as good a plan as any.
If both of your apps are Java, you could use OSCache (supported by
iBATIS) to implement a distributed cache strategy. Otherwise a
messaging solution would allow you to notify disparate systems of
significant data changes and then flush the cache.
Cheers,
Clinton
On Thu, 3 Feb 2005 09:59:25 +0200, Sergey Livanov
<Se...@ukrpost.net> wrote:
>
> Could you please help me figure out the cache scheme.
> When I'm within one application I can use the flush method.
> How should I correctly develop a cashing scheme if data is saved by one
> application and displayed by another? Would it be helpful to have a
> signal record that I initially read from the database and then,
> if the data changed, do a forced flush?
>
> --
> regards,
> Sergey mailto:Sergey.Livanov@ukrpost.net
>
>