Howto manage object-livecycle in distributed systems?

Hi there,

I am currently working on a distributed clients-server system where a GUI resides on the clients whereas the programmer programs to server-side dummies like the GUI would be running local.

Therefor I map between client-side-Implementation and server-side-dummy using object-IDs:

client-side-widget-implementation network (only ID is transferred) server-side-dummy-object

The problem I have is that I would like a system without forcing the programmer to explicitly dispose an object (since both sides don't know wether the object is still visible on the other side). How did RMI solve this issue and are there some clever designs to avoid this problem?

Thank you in advance, lg Clemens

[734 byte] By [linuxhippya] at [2007-11-27 3:07:02]
# 1
There are only three possibilities: dispose/destroy, timeouts or wait for GC.And timeouts are probably required regardless.
jschella at 2007-7-12 3:53:47 > top of Java-index,Other Topics,Patterns & OO Design...