3 ms·
Actually if you use the low-level LWIP (sometimes called Raw API) instead of the socket API it will be actually event-driven (singlethreaded, callback-driven, e
by Matthias247 9y ago
Actually if you use the low-level LWIP (sometimes called Raw API) instead of the socket API it will be actually event-driven (singlethreaded, callback-driven, etc.) by design. The socket abstraction layer on top of it then provides blocking APIs and multithreading support - with the cost of a lower performance.
- MrBuddyCasino 9y agoI'm planning to eventually migrate to the netconn API, but was deterred by a lack of documentation. Do you know of any sources? This doesn't help much: http://www.nongnu.org/lwip/2_0_x/index.html http://www.nongnu.org/lwip/2_0_x/index.html
- Matthias247 9y agoI also had quite some hard time with the lack of documentation for LWIP. The only other source that I found was the Wiki which is also linked there: http://lwip.wikia.com/wiki/LwIP_Wiki http://lwip.wikia.com/wiki/LwIP_Wiki But I still had to figure out lots of things from the actual code.
- MrBuddyCasino 9y agoRats. I had a feeling you'd say that, thanks!
- Matthias247 9y agoI found something more in my work bookmarks: http://www.atmel.com/Images/Atmel-42233-Using-the-lwIP-Network-Stack_AP-Note_AT04055.pdf http://www.atmel.com/Images/Atmel-42233-Using-the-lwIP-Netwo... Maybe it also has some extra information which can help.
- MrBuddyCasino 9y agoThanks!