lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: mat henshall
Subject: Re: [lwip-users] lwIP RAW API and "deferred processing" indifferentcontext
Date: Wed, 7 Dec 2011 21:45:11 -0800

You may want to look at the QP statemachine framework (www.state-machine.com) for a reasonable very light weight framework that can be used with NO_SYS - the author has an example using lwIP.




On Wed, Dec 7, 2011 at 9:27 PM, Ueli Niederer <address@hidden> wrote:
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


_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users



--

Mat Henshall
Founder and CEO, Square Connect, Inc.
San Jose, CA
www.squareconnect.com
cell: 650.814.7585

reply via email to

[Prev in Thread] Current Thread [Next in Thread]