hi,
looking at the code of accept in sbcl, it seems that it may return with nil in case of sockint::EAGAIN or sockint::EINTR.
what should usocket do in this case? loop until non-nil is returned or return nil?
the latter might be more useful when dealing with timeouts, but i'm no socket expert of any kind.
On 6/16/07, Attila Lendvai attila.lendvai@gmail.com wrote:
hi,
looking at the code of accept in sbcl, it seems that it may return with nil in case of sockint::EAGAIN or sockint::EINTR.
what should usocket do in this case? loop until non-nil is returned or return nil?
I've given the issue quite a bit of thought and I think it would be single-thread-multiplexing application friendly to return NIL from usocket too.
the latter might be more useful when dealing with timeouts, but i'm no socket expert of any kind.
Time-outs as well as other signals and idle-processing. Thanks for the pointer, I'll need to verify usocket's behaviour in this respect.
bye,
Erik.
-
Attila Lendvai -
Erik Huelsmann