The other option, which tends to be the easiest, is to use a per-broker cache (non-distributed) and optimistic transactions, in which case you acknowledge that data in cache for the lifetime of one broker (usually short depending on how you use it) may be dirty if ti is in contention. This doesn't work for highly contentious data, however.
-Brian
On Apr 29, 2004, at 5:30 AM, Amol Pophale wrote:
Hi All, I just learned OJB. I have written one application in OJB. My application is client-server application in which client and server are on different machines and using same databse which may be on third machine. Right now i have one query. server stores some java object in databse using PersistaceBroker APIs. Client retrives these object on its machine using same i.e. OJB Now if any object is updated by server which is in client object cache How can we update client object cache when server updates the object in database. Because I think server cache and client cache are different. I need this very urgent.
Thanks in advance Amol Pophale.
____________________________________________________________ Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html
--------------------------------------------------------------------- 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]
