Basics
======

The netio3 API consists of 4 main classes for sending, receiving,
publishing and subscribing. Communication is asynchronous in all
implemented back-ends and provides hooks for user supplied callbacks at
connection established/closed, transfer complete etc.

For most actions, the netio3 library does not use exceptions but
methods return status codes (:cpp:enum:`netio3::NetioStatus`) or
(:cpp:enum:`netio3::NetioPublisherStatus`) which should be checked by
the caller.

..  LocalWords:  netio3