Originally posted by Siddharth Mehrotra:
i have been reading a lot about connection manager on this board.
can anyone explain me why is there a need of connection manager.
if i bind the remoteImp of data class with the rmi registry. everone will be able to share the object.
and if i plan to use a lockManager for maintaining the lock records, then even there , there should be only one object of lock manager that muct be used by the remoteData class.
so whats the need of a connection manager
Originally posted by karthik Guru:
Thanks for pointing out the usefulness of the unreferenced intereface. This one is a nice feature i was'nt aware of.
Unfortunately i did'nt use it when i did my SDCD (some 7 months back!)
anyway i have a question for you.
I remember that i had implemented forced unlocking after a timeout.
I understand that in your case if the client crashes, you can take appropriate action and release the lock.
Did u have a forced unlock by any chance?
Do you think anything can be done, if the client chose to ignore the "lock-read-modify-unlock" sequence (ie ignored the unlock ("just a wierd possibility")).
How did you do client identification?
is your identification based on the passing objects between client and server?
OR did you implement Callbacks?