Mag
Mag
Peter den Haan | peterdenhaan.com | quantum computing specialist, Objectivity Ltd
Originally posted by Darryl Cheung:
Please comment if that looks correct!
Now, I have one DataRemoteImpl object per client which can uniquely identify itself to the lock manager when locking.
Originally posted by HS Thomas:
Daryl,
In your amended version , does your DataRemoteImpl still have to extend UnicastRemoteObject ?
Does the connection manager create a new DataRemoteImpl object each time the same client calls it ? If so, how can you ever detect the same object reference to unlock the record locked by the same client ?
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |