Hi Kaspar, 2015-05-08 11:09 GMT+02:00 Kaspar Schleiser <kas...@schleiser.de>:
> Hi, > > 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? > Actually, yes. But I'm still trying to get my head around why netapi (or it's wrapper functions [1], slightly renamed) could not be that API. Cheers, Martine [1] https://github.com/RIOT-OS/RIOT/blob/master/sys/include/net/ng_netapi.h
_______________________________________________ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
