On Sep 09, 2015, at 02:29 PM, "address@hidden" <address@hidden> wrote:
Joel Cunningham wrote:
I like the idea, maybe an apps folder under src?
Something like that, yes.
I am curious about what the criteria will be for accepting new apps.
It seems that applications using the RAW API are unique to LwIP, but
applications written against the BSD sockets interface could work with
other stacks and may not be very unique to LwIP. Would apps
lightweight in nature be enough for inclusion?
In my opinion, they would be RAW API applications. I'm personally not a
big fan of the netconn API as I think the zero-copy feature being the
only difference to the socket API is not enough advantage to maintain an
own API for it. As such, I wouldn't want to maintain netconn apps.
Aside from that, an application must of course either have a maintainer
or must be easy enough for others to understand/maintain.
This makes sense to me as well :)
One final thought, we could potentially move the DHCP client into this
folder since it is indeed a layer 5 protocol. Other stacks implement
the DHCP client (and server) outside of the TCP/IP stack itself.
Well, with these protocols (DNS as well) you could argue. However, DHCP
is too integrated into the stack (e.g. input processing, AutoIP
integration) for me to handle it as an applications, although it is L5.
Or at least, moving it to "apps" would mean more work to cleanly make
the core code not depend on it.
Agreed, it's nice from an architectural purity standpoint, but practically, it might just be a waste of time to move it out
Joel