i think that for unusual servers, including filters, it's easier just to serve
the protocol, rather than try to second-guess an otherwise helpful library.
--- Begin Message ---
> I want each clunk, not the last one...
there will be at most one clunk for an open
file, as it's illegal to clone an open fid.
in the usual case (when clients are being non-malicious)
destroyfid on an open file will be trigged
by that clunk.
it does seem a pity that there seems to
be no way of delaying the response to a clunk
without stopping the server read loop.
--- End Message ---
