Comment 4 for bug 738188

The above idea wouldn't work, since the object's not available after deletion (using weakref.ref with a callback, not __del__). A better idea (one that should actually be workable) is to have a version attached to objects. Whenever the owner of the object marshals the object, it increments the version by one. When the proxy is deleted, it sends a "delete" message to the owner with the version. If the version matches the latest version, the object is really deleted. Otherwise, the object is resent, resetting the version to zero.

I'm working on this (slowly - pesky day job). It's a bit rough at the moment, and awfully slow (2x slower than the 0.4 release), so I don't expect to be doing much else for the next release.