http://jakarta.apache.org/jcs/LateralTCPProperties.html
Set issueRemoveOnPut to true to only send a remove and not a put. IssueRemoveOnPut If this is set to true, then the lateral client will send a remove command rather than a put command to any registered listeners. N false Also set FilterRemoveByHashCode to true. FilterRemoveByHashCode If this is true, and IssueRemoveOnPut is true, the client will include the hashCode of the element to remove. If it is also true on the receiving end, the receiver will check to see if the element exists. If the element exists, and the hashCodes are the same, the item will not be removed. N false > -----Original Message----- > From: Nirlesh Patel [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 29, 2005 5:05 PM > To: [email protected] > Subject: Exactly what data is exchanged between lateral caches for PUTs? > > Hello > > I am trying to use the TCP Lateral cache and have a question about exactly > what data is exchanged between lateral caches when AllowGet=FALSE > > The documentation says that "False means that it can only put, i.e. send > updates and remove requests to other laterals." > > So when an object is put into cache WHAT is sent to the other laterals ? > > - The cached object, its key and region > - Just the key and region > - ??? > > Basically I want to minimize network traffic since the lateral caches are > across physical separate sites - What I really need is to let laterals > know > when a remove has happened so that I don't have stale cached data anywhere > - is it possible to configure the lateral cache to do this. > > Thanks > NP > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
