Re:Using select(2) the right way
by Matthias247 on Monday June 05, 2017 @09:34AM
(#14487456)
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.
[ Parent
| on HN ]
Re:Using select(2) the right way
by MrBuddyCasino on Monday June 05, 2017 @12:20PM
(#14488821)
I'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
Re:Using select(2) the right way
by Matthias247 on Monday June 05, 2017 @04:35PM
(#14491669)
I 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
But I still had to figure out lots of things from the actual code.
Re:Using select(2) the right way
by MrBuddyCasino on Tuesday June 06, 2017 @03:17AM
(#14495374)
Rats. I had a feeling you'd say that, thanks!
Re:Using select(2) the right way
by Matthias247 on Wednesday June 07, 2017 @03:46AM
(#14504401)
I found something more in my work bookmarks: http://www.atmel.com/Images/Atmel-42233-Using-the-lwIP-Netwo...
Maybe it also has some extra information which can help.
Re:Using select(2) the right way
by MrBuddyCasino on Wednesday June 07, 2017 @10:20AM
(#14506629)
Thanks!