This time it's on windows. Still 2.38.
I have a stream that has been closed from the other side
and socket:SOCKET-STATUS generates an error:
Winsock error 10054 (ECONNRESET): Connection reset by peer
I thought that socket-status (at least on a socket stream)
was never supposed to cause an error.
The stream still appears open to lisp, even after the error above.
The doc is slightly ambiguous here.
We define status for a SOCKET:SOCKET-SERVER or a SOCKET:SOCKET-STREAM
to be :ERROR if any i/o operation will cause an ERROR.
That could mean either
if ALL operation will cause errors
if SOME operations will cause errors.
The second seems more plausible to me. In fact, I suspect it really
means that if the code trying to compute socket-status generates an
error, then the value will be :error.
But then the Winsock error above should cause status to be :error.
I haven't checked the error yet on linux. In fact, it may be
difficult to check since not every client generates the error
and I currently can't accept connections from other machines
(due to earlier mentioned problem).
Get latest updates about Open Source Projects, Conferences and News.