Re: [lwip-users] Non-blocking netconn callback and TCP accept backlog

[address@hidden]

Nick Brereton wrote:
> As I have understood it data should not start flowing until I have accepted the 
> connection (presumably completion of the handshake should be delayed until  the 
> netconn_accept call, thus preventing the client from sending any data?) and the 
> connection should be sitting in the tcp listen queue.

I think it's rather different and the handshake is completed directly 
before the 'accept' callback is called. That would mean the client can 
send data even while you have enqueued the new connection. I haven't 
really worked that way, though. I also don't know how other socket 
implementations handle this...

Simon