[riot-devel] Network API task force
kaspar at schleiser.de
Fri May 8 11:09:33 CEST 2015
On 05/08/15 10:58, Martine Lenders wrote:
> just to state the "opposite" opinion, too: while I see the need for an API
> suitable for embedded use only and other stacks than the default one too,
> I'm of the opinion, that the POSIX sockets (needed for library and
> application ports) should also be as slim as possible. This means: A
> wrapper (POSIX sockets) around a wrapper (the new new network API) around
> some API (e. g. netapi) seems like overkill to me.
If you agree that we need an API for embedded use, would you agree that
this API should be the one that all RIOT internal libraries (e.g., for
CoAP) should use?
More information about the devel