diff options
| author | Jonas Schnelli <dev@jonasschnelli.ch> | 2016-03-29 14:30:02 +0200 |
|---|---|---|
| committer | Jonas Schnelli <dev@jonasschnelli.ch> | 2016-04-19 15:32:11 +0200 |
| commit | 0b25a9fb42d5df54ea35ddb2bb4837e1e29355fd (patch) | |
| tree | 429fe7843fbb85f3d46653381d0f82a39a4be595 /doc | |
| parent | de821d56e1f458fbe580520c77ac066107f4d77c (diff) | |
[ZMQ] append a message sequence number to every ZMQ notification
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/release-notes.md | 9 | ||||
| -rw-r--r-- | doc/zmq.md | 5 |
2 files changed, 14 insertions, 0 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md index 806d174ebf..9fb1a13072 100644 --- a/doc/release-notes.md +++ b/doc/release-notes.md @@ -45,6 +45,15 @@ The following outputs are affected by this change: - REST `/rest/block/` (JSON format when including extended tx details) - `bitcoin-tx -json` +### ZMQ + +Each ZMQ notification now contains an up-counting sequence number that allows +listeners to detect lost notifications. +The sequence number is always the last element in a multi-part ZMQ notification and +therefore backward compatible. +Each message type has its own counter. +(https://github.com/bitcoin/bitcoin/pull/7762) + ### Configuration and command-line options ### Block and transaction handling diff --git a/doc/zmq.md b/doc/zmq.md index 902d1124c7..8d795a388a 100644 --- a/doc/zmq.md +++ b/doc/zmq.md @@ -99,3 +99,8 @@ using other means such as firewalling. Note that when the block chain tip changes, a reorganisation may occur and just the tip will be notified. It is up to the subscriber to retrieve the chain from the last known block to the new tip. + +There are several possibilities that ZMQ notification can get lost +during transmission depending on the communication type your are +using. Bitcoind appends an up-counting sequence number to each +notification which allows listeners to detect lost notifications. |