Heikki Linnakangas <hlinnakangas@vmware.com> writes:
> I was going to suggest using WaitLatchOrSocket instead of sleeping in 1
> second increment, but I see that WaitLatchOrSocket() doesn't currently
> support waiting for a socket to become writeable, without also waiting
> for it to become readable. I wonder how difficult it would be to lift
> that restriction.
My recollection is that there was a reason for that, but I don't recall
details any more.
regards, tom lane