Re: [lwip-devel] Netconn events?

[Joel Cunningham]

> On Oct 11, 2016, at 2:38 PM, address@hidden wrote:
> 
> Joel Cunningham wrote:
>> +1 on throwing away netconn and having cleaner socket implementation :)
> 
> :-) I had that idea long time ago, but haven't found the time to do it so 
> far...
> 
>> If I'm not mistaken, netconn was the original top level API and sockets were 
>> bolted on later.  Does anyone know/remember the details?
> 
> I think it was like that, yes. However, I have missed the first years of 
> community development of lwIP, so I can't tell for sure...
> However, the question is can we safely get rid of the netconn API, or could 
> it coexist with an improved socket API for some time.
> 

The netconn API could probably co-exist with a re-written sockets API.  You’d 
have duplication of some things (blocking of calling threads, storing received 
packets, processing of events), but maybe that’s a fair trade-off for systems 
that have old netconn applications.  When the re-written sockets API is 
released, the netconn API could be marked as deprecated and then actually 
removed in a following release.  This would give systems using netconn 
applications time to migrate, while not forcing the LwIP community to maintain 
the netconn API till the end of time.

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

Joel