Re: [lwip-users] lwIP RAW API and "deferred processing" indifferentcontext

[Ueli Niederer]

Quoting Kieran Mansley <address@hidden>:
> lwIP already has more specialised APIs that are tailored to deliver  
> higher performance and lower overheads, which people are encouraged  
> to use,
What I am thinking about is if it would be helpful to have a small  
framwork doing the listen- and worker-thread management for us and  
only leaves the whole "Protocol handling strategy" up to the  
developer. I think this would be helpful as this pattern is widely  
used and re-implemented very often. I also think one could arrange the  
code of this framework so you you can port your application between  
"NO_SYS=1" and "NO_SYS=0" with practically zero changes.

I think I'll sit down in a week or two and try to design something  
useful for this case. Maybe this would then be interesting to  
integrate with lwIP too?

> but the sockets API needs to be as close to the BSD sockets standard  
> as possible.
totally agreed. I was first thinking of how to implement BSD sockets  
in a non-blocking way and ended up with exactly this thought: If it's  
not blocking anymore, it's not BSD anymore, so you and up writing you  
application twice anyway. That would not help.

Regards
Ueli