Pipe represents one "connection", i.e. perfectly ordered uni- or
bi-directional stream of messages. One endpoint can create multiple pipes
(for example, bound TCP socket is an endpoint, individual accepted TCP
connections are represented by pipes.
This value is returned by pipe's send and recv functions to signalise that
more sends/recvs are not possible at the moment. From that moment on,
the core will stop invoking the function. To re-establish the message
flow nn_pipebase_received (respectively nn_pipebase_sent) should
be called.
The base class for pipes:
Pipe represents one "connection", i.e. perfectly ordered uni- or bi-directional stream of messages. One endpoint can create multiple pipes (for example, bound TCP socket is an endpoint, individual accepted TCP connections are represented by pipes.
This value is returned by pipe's send and recv functions to signalise that more sends/recvs are not possible at the moment. From that moment on, the core will stop invoking the function. To re-establish the message flow nn_pipebase_received (respectively nn_pipebase_sent) should be called.