Exactly, the client needs to know which objects the server still references, to be able to clear refrences to them.
I've written a rmi-like framework for swing components (its especially tuned for swing and not based on RMI):
http://juibrowser.sf.net/demo.html
It also uses distributed GC, but the problem is even more critical because the server stores only lightweight half-objects, whereas on the client the couterparts are real swing-objects which often weight a few kB. So the server could create millions of UButtons, but the client is OOM after a few hundred thousands.
For such enviroments I would use CMS collector if pauses are critical, and a small nurse/eden space.
This will guarantee frequent GCs, but also impact throughtput negativly.
lg Clemens
[Message sent by forum member 'linuxhippy' (linuxhippy)]
http://forums.java.net/jive/thread.jspa?messageID=275832