Comment 2 for bug 674395

Oh. I understand. My mistake is to wait IOTimeout error while reading
from socket and in sbcl 1.0.41 i got it. But as i understand it is
undocumented feature. So now i have a question. How I can get such
behaviour using stable documented features?

2010/11/18 Nikodemus Siivola <email address hidden>:
> Can you provide some more details please? (A test-case would be
> perfect.)
>
> Timeouts on sockets (and fd-streams in general) apply only to wait-
> periods when reading new input -- admittedly this is not properly
> documented at the moment.
>
> So :timeout 0.1 means: "signal a timeout if there is no new input for
> 0.1 seconds", not "must be closed in 0.1 seconds".
>
>
> ** Changed in: sbcl
>       Status: New => Incomplete
>
> --
> Timeouts on sockets does not work
> https://bugs.launchpad.net/bugs/674395
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Steel Bank Common Lisp: Incomplete
>
> Bug description:
> Timeouts doesnt work for 1.0.44 sbcl in socket-make-stream (for socket-connect sockets). And timeouts for socket-accept doesnt works in 1.0.41 nor 1.0.44
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/sbcl/+bug/674395/+subscribe
>

--
С уважением, Кукушкин Павел.
Программист ООО "Ехать"