Changeset View
Changeset View
Standalone View
Standalone View
doc/zmq.md
Show First 20 Lines • Show All 89 Lines • ▼ Show 20 Lines | |||||
These options can also be provided in bitcoin.conf. | These options can also be provided in bitcoin.conf. | ||||
ZeroMQ endpoint specifiers for TCP (and others) are documented in the | ZeroMQ endpoint specifiers for TCP (and others) are documented in the | ||||
[ZeroMQ API](http://api.zeromq.org/4-0:_start). | [ZeroMQ API](http://api.zeromq.org/4-0:_start). | ||||
Client side, then, the ZeroMQ subscriber socket must have the | Client side, then, the ZeroMQ subscriber socket must have the | ||||
ZMQ_SUBSCRIBE option set to one or either of these prefixes (for | ZMQ_SUBSCRIBE option set to one or either of these prefixes (for | ||||
instance, just `hash`); without doing so will result in no messages | instance, just `hash`); without doing so will result in no messages | ||||
arriving. Please see `contrib/zmq/zmq_sub.py` for a working example. | arriving. Please see [`contrib/zmq/zmq_sub.py`](/contrib/zmq/zmq_sub.py) for a working example. | ||||
## Remarks | ## Remarks | ||||
From the perspective of bitcoind, the ZeroMQ socket is write-only; PUB | From the perspective of bitcoind, the ZeroMQ socket is write-only; PUB | ||||
sockets don't even have a read function. Thus, there is no state | sockets don't even have a read function. Thus, there is no state | ||||
introduced into bitcoind directly. Furthermore, no information is | introduced into bitcoind directly. Furthermore, no information is | ||||
broadcast that wasn't already received from the public P2P network. | broadcast that wasn't already received from the public P2P network. | ||||
Show All 14 Lines |