Hi,

> When it is set to false, does it mean that
>changes made in other caches are ignored and stale objects can be
>returned?
Yes, I think that when RemoveUponRemotePut=false, if the object is in
your local cache it will use this, even if this is stale compared to
your remote cache. When the data in your local cache expires it goes off
to the remote cache and checks there, picking up your latest version,
therefore eventually catching up.

>Also, when it is true,
>changes made in other caches causes the value to be set as null. When
>a get is made on the same key, does it retrieve the value from the
>remote cache?
Yes, from what I have seen, if RemoveUponRemotePut=true and you put
something in your local cache, lets call it cache A, that object is
propagated to the remote cache, and if the object key is in another
local cache, say cache B, it is removed from cache B (if it was there).
When cache B tries to get the object using the same key, it doesn't have
it anymore in its local cache, so goes to the remote cache and gets it
from there, storing it after retrieval in local cache B for future use
so it doesn't have to go back to the remote cache, until the next put
causes a removal again.

Regards,
Simon

-----Original Message-----
From: Chandri Krishnan [mailto:[EMAIL PROTECTED] 
Sent: Monday, August 20, 2007 10:23 PM
To: JCS Users List
Subject: Re: asynchronous updates

Thanks Simon, that works! I'm not sure I understand the semantics of
RemoveUponRemotePut. When it is set to false, does it mean that
changes made in other caches are ignored and stale objects can be
returned? In what scenario is this useful? Also, when it is true,
changes made in other caches causes the value to be set as null. When
a get is made on the same key, does it retrieve the value from the
remote cache?

Thanks,
Chandri

On 8/20/07, Horton Simon <[EMAIL PROTECTED]> wrote:
> Hi Chandri,
>
> Have you tried setting the RemoveUponRemotePut=true to see if that
> resolves your issue? (Your RServer and RCluster have this attribute
> specified below)
>
> Regards,
> Simon
>
> -----Original Message-----
> From: Chandri Krishnan [mailto:[EMAIL PROTECTED]
> Sent: Monday, August 20, 2007 6:19 PM
> To: jcs-users@jakarta.apache.org
> Subject: Re: asynchronous updates
>
> A small correction in my previous email. The sizes of my objects vary
> from 8-12KB.
>
> Chandri
>
> On 8/16/07, Chandri Krishnan wrote:
> > Hello,
> >
> > I am having as issue with a prototype distributed cache that I am
> > building with JCS. I am running JCS with one remote server and two
> > clients. I am using a standalone driver that communicates with these
> > clients. The clients create, retrieve, update and remove hundreds of
> > objects (each of size few hundred bytes) based on commands received
> > from the driver.
> >
> > I noticed that some objects inserted into the cache in one client is
> > not available from the other. Sometimes updates aren't reflected. I
> > looked at all the cached objects in both the caches using
> > cache.getGroupKeys and the numbers are never the same. Shouldn't the
> > updates be available immediately to both the clients? I found that
> > puts and removals occur asynchronously with the Remote server
setting,
> > but gets are synchronous.
> >
> > Any help will be appreciated.
> >
> > Thanks,
> > Chandri
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


This message and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this message in error please delete it and any files 
transmitted with it, after notifying [EMAIL PROTECTED] 
Any opinions expressed in this message may be those of the author and not 
necessarily those of the company. The company accepts no responsibility for the 
accuracy or completeness of any information contained herein. This message is 
not intended to create legal relations between the company and the recipient. 
Recipients should please note that messages sent via the Internet may be 
intercepted and that caution should therefore be exercised before dispatching 
to the company any confidential or sensitive information. 
Mizuho International plc Bracken House, One Friday Street, London EC4M 9JA. 
TEL. 020 72361090. Wholly owned subsidiary of Mizuho Securities Co., Ltd. 
Member of Mizuho Financial Group. Authorised and regulated by the Financial 
Services Authority. Member of the London Stock Exchange. 

Registered in England No. 1203696. Registered office as above.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to