Amol,
I think you face and underlying problem related to the architecture of
your application.
I do not know if you are familiar with the MVC pattern, but it seems
considering applying it to your project might be of help.
The basic idea is to let the Controller in the server "talk" to the Model
You are effectively operating in a cluster, where your workstations are
also cluster nodes:
http://db.apache.org/ojb/howto-work-with-clustering.html
-Brian
On Apr 29, 2004, at 7:53 AM, Amol Pophale wrote:
Hi Brain
Thanks a lot for urgent reply.
You said I need to use one of the distributed cac
Hi Brain
Thanks a lot for urgent reply.
You said I need to use one of the distributed caches
(JCS, OSCache, or Coherence)
can u please tell where i can get details info about
this or if u know can u tell me by some example or
where can i get that API help etc.
I mean more detail.
Note:do u anythin
You need to use one of the distributed caches (JCS, OSCache, or
Coherence).
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
shor
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
Per
