>Do you do completely asynch clunks or just the wait for the response?. it uses `completely' async clunks, which is why it can be broken.
having the original process send the Tclunk and not wait for the Rclunk is different. i think it was mentioned last time this matter came up, and that's probably why i didn't pursue this discussion further then, since that change is less of a problem. (at least, if you don't mind close not returning an error from the clunk, but since the current implementations suppress errors from clunk, it's a trickier position to sustain.)
