[riot-devel] Network API task force

Oleg Hahm oliver.hahm at inria.fr
Fri May 8 14:48:08 CEST 2015

Hi Kaspar!

> int ng_netapi_send(kernel_pid_t pid, ng_pktsnip_t *pkt);
> If we omit the messaging, and the pktbuf dependency, it is not "netapi"
> anymore.

For me netapi are basically four functions send(), set_receive_cb(), get() and
set(). This can be implemented as wrapper functions around IPC (as in the
nameless stack) or as direct function calls.
> Also, the default stack's whole design is based on threads passing
> messages containing pktsnips. Changing that would change the whole concept.

And nobody wants to do this.

> Applications now should be written in a network stack agnostic way.
> So if the stack implementor decides to go for the benefits of having
> clear module seperation and flexibility through using messages and
> threads, that still shouldn't force our application interfaces to that
> decision.


The problem with token ring jokes is you need to wait your turn to laugh
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.riot-os.org/pipermail/devel/attachments/20150508/6b0dc7d3/attachment.sig>

More information about the devel mailing list