Re: [lwip-users] socket functionality - nonblocking?

[Kieran Mansley]

On Mon, 2008-11-24 at 16:52 +0100, Micael wrote:
> Basically, I need non-blocking connect, recv, select and listen.
> 
> From what I gather from various posts on this list, connect() maybe does
> not do non-blocking, and I therefore assume that maybe recv doesn't
> either. This part is a bit hard to read out from the code, being new to
> this stack.

>From memory (please correct if I'm wrong) I think we have:

connect: blocking
recv: non-blocking or blocking
select: non-blocking or blocking with timeout
listen: blocking

Also note however that we don't support a full version of select: it
will return when a socket becomes readable or writeable, not not when
there exceptions.  I'm not sure if you can put a listening socket in the
readable set and get notified when a new connection arrives either -
perhaps someone else has recent experience of this.

Kieran