I think I was questioning the generation of an exception for this particular
condition. It didn't appear to be severe or exceptional enough to me when I
was looking at the code. Seems more reasonable now, however.
Date: Tue, 29 May 2001 12:16:01 -0400
I've written a little server that uses read- string/partial to get data
from clients. The server waits in select until data is available, then
reads from the sockets that select has indicated are readable.
Sometimes, the read system call on a client socket returns -1 with errno
set to ECONNRESET, since a client has closed its communications socket.
The code in generic-read-string!/partial does not catch this case, so my
server was dying. Is this a bug in read- string/partial?
I would say not. It's your r-s!/p procedure telling you something unusual
I now wrap read-string/partial as follows, which has
made the problem go
(define (read-carefully port)
((err data) ((errno/connreset) #f))
(read-string/partial 1024 port)))
Is this the right approach?
Since you don't care this case, yes.