diff options
| author | Wladimir J. van der Laan <laanwj@gmail.com> | 2016-04-19 15:36:58 +0200 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2016-04-19 15:44:38 +0200 |
| commit | a1eb344ba8f4ef7dade755c823a9d001f837ae7d (patch) | |
| tree | d063a57050a83688d042ceb308066c64dbbd9da8 /doc/zmq.md | |
| parent | 0e6fd5e4af31ada6da8df006801b59e9178ecd85 (diff) | |
| parent | 0b25a9fb42d5df54ea35ddb2bb4837e1e29355fd (diff) | |
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/zmq.md')
| -rw-r--r-- | doc/zmq.md | 5 |
1 files changed, 5 insertions, 0 deletions
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. |