JayT106
d4cda544ae
|
3 years ago | |
|---|---|---|
| .. | ||
| types | 3 years ago | |
| CONTRIBUTING.md | 4 years ago | |
| README.md | 5 years ago | |
| abci.go | 4 years ago | |
| blocks.go | 3 years ago | |
| blocks_test.go | 3 years ago | |
| consensus.go | 3 years ago | |
| dev.go | 3 years ago | |
| doc.go | 4 years ago | |
| doc_template.txt | 7 years ago | |
| env.go | 3 years ago | |
| env_test.go | 4 years ago | |
| events.go | 3 years ago | |
| evidence.go | 4 years ago | |
| health.go | 4 years ago | |
| mempool.go | 3 years ago | |
| net.go | 3 years ago | |
| net_test.go | 3 years ago | |
| routes.go | 3 years ago | |
| status.go | 3 years ago | |
| tx.go | 4 years ago | |
README.md
Tendermint RPC
Pagination
Requests that return multiple items will be paginated to 30 items by default. You can specify further pages with the ?page parameter. You can also set a custom page size up to 100 with the ?per_page parameter.
Subscribing to events
The user can subscribe to events emitted by Tendermint, using /subscribe. If
the maximum number of clients is reached or the client has too many
subscriptions, an error will be returned. The subscription timeout is 5 sec.
Each subscription has a buffer to accommodate short bursts of events or some
slowness in clients. If the buffer gets full, the subscription will be canceled
("client is not pulling messages fast enough"). If Tendermint exits, all
subscriptions are canceled ("Tendermint exited"). The user can unsubscribe
using either /unsubscribe or /unsubscribe_all.