> Right now, if you have a partition between client and server A, I would not
> server A to see a clean close from the client, but one of the various
> that cause the socket to close.
Please don't get me wrong, but I find it very funny to rely on the
stability of a network partition to avoid having a session killed.
Either way, that's not a big deal for me, now that I understand the
problem. Knowing about it, I can simply postpone the close() until a
safe time. It just felt worth pointing out, since this will arguably
be *very* hard to track down in practice.