forked from TrueCloudLab/neoneo-go
docs: add ordering guarantees for notary request events
Signed-off-by: Anna Shaleva <shaleva.ann@nspcc.ru>
This commit is contained in:
parent
81a439a0d6
commit
e3aa6bba4d
1 changed files with 4 additions and 0 deletions
|
@ -41,6 +41,10 @@ Filters use conjunctional logic.
|
||||||
they're in the block. After all in-block transactions announcements PostPersist
|
they're in the block. After all in-block transactions announcements PostPersist
|
||||||
script execution is announced followed by notifications generated during the
|
script execution is announced followed by notifications generated during the
|
||||||
script execution. Finally, block announcement is followed.
|
script execution. Finally, block announcement is followed.
|
||||||
|
* notary request events announcements are not bound to the chain processing.
|
||||||
|
Trigger for notary request notifications is notary request mempool content
|
||||||
|
change, thus, notary request event is announced every time notary request
|
||||||
|
enters or leaves notary pool.
|
||||||
* unsubscription may not cancel pending, but not yet sent events
|
* unsubscription may not cancel pending, but not yet sent events
|
||||||
|
|
||||||
## Subscription management
|
## Subscription management
|
||||||
|
|
Loading…
Reference in a new issue