| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
While here addressed some minor issues with http docs as well.
|
| | |
|
| |
|
|
|
| |
One must not attempt to use any functions that access the socket
directly from pipe notification callbacks.
|
| | |
|
| |
|
|
| |
- Update nng_pipe_notify manpage including copyright
|
| |
|
|
|
|
|
|
|
|
|
|
| |
fixes #494 ERRORS section should use [horizontal]
These changes address some basic formatting consistency things,
and ultimately (when combined with other tooling changes that are
not part of this repo) lead to vastly improved layout in the
printed documentation.
While here we removed trailing whitespace, and did certain other
minor markup tweaks.
|
| |
|
|
|
|
|
|
|
| |
This changes the signature of nng_pipe_notify(), and the associated
events. The documentation is updated to reflect this.
We have also broken the lock up so that we don't hold the master
socket lock for some of these things, which may have beneficial
impact on performance.
|
|
|
This adds a new pipe event notification API (callbacks called
on either pipe add or remove), including both tests and docs.
Also supporting APIs to get the socket or endpoint associated
with a pipe are included (tested and documented as well.)
|
