[Resending. Originally sent 9/25 but it bounced!]
> If we complete a partial write and then timeout, we return -1. This
> doesn't give the caller any chance to update their data pointers and
> re-issue the call.
Except for timeouts, network I/O errors are usually unrecoverable,
meaning that trying again won't help. I agree that when a network I/O
operation times out after a partial success there ought to be a way to
determine how much succeeded. As Gene suggested, write your own -- and
then contribute it to the project for all to share.
[Actually I have coded up a version of this in the interim but haven't
tried it yet. Anyone want to test it for me?]
However this is not John Val's original issue, which was that the
timeout seems to trigger early. John, can you post a minimal program
that exhibits the undesirable behavior so we can diagnose it? Can you
make it happen with just a single state thread? Alternatively you could
trace through the execution of the ST code yourself, watching for
erroneous behavior, and ask for more specific help.
--
Michael J. Abbott mja@xxxxxxx www.repbot.org/mike
|