diff options
| author | Wladimir J. van der Laan <[email protected]> | 2016-04-19 15:36:58 +0200 |
|---|---|---|
| committer | Wladimir J. van der Laan <[email protected]> | 2016-04-19 15:44:38 +0200 |
| commit | a1eb344ba8f4ef7dade755c823a9d001f837ae7d (patch) | |
| tree | d063a57050a83688d042ceb308066c64dbbd9da8 /doc | |
| parent | Merge #7822: Add listunspent() test for spendable/unspendable UTXO (diff) | |
| parent | [ZMQ] append a message sequence number to every ZMQ notification (diff) | |
| download | discoin-a1eb344ba8f4ef7dade755c823a9d001f837ae7d.tar.xz discoin-a1eb344ba8f4ef7dade755c823a9d001f837ae7d.zip | |
Merge #7762: [ZMQ] append a message sequence number to every ZMQ notification
0b25a9f [ZMQ] append a message sequence number to every ZMQ notification (Jonas Schnelli)
de821d5 [ZMQ] refactor message string (Jonas Schnelli)
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 8360cc481..73ad13e72 100644 --- a/doc/release-notes.md +++ b/doc/release-notes.md @@ -52,6 +52,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 902d1124c..8d795a388 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. |