StakeSquid/dshackle
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Upstream configuration improvement: (#149)

Browse Source 
- now we can specify connector mode for better fine tuning of connection
This commit is contained in:
a10zn8
2023-02-27 14:22:50 +05:00
committed by GitHub
parent 1ec3d44484
commit 00a1490726
14 changed files with 220 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
docs/04-upstream-config.adoc
View File

@@ -190,6 +190,27 @@ Dshackle currently supports
- `ws` websocket connection (supposed to be used in addition to `rpc` connection)
- `grpc` connects to another Dshackle instance
==== Connection mixture modes
In case of rpc and ws connection we can specify different modes of works together:
|===
|Type |Description
|WS_ONLY
|Default mode in case WS endpoint specified. In this mode WS connection is used for all requests and subscriptions.
|RPC_ONLY
|Default in case WS endpoint not specified. In this mode RPC connection is used for all requests, subscriptions doesn't work, head subscription works through scheduled RPC head request.
|RPC_REQUESTS_WITH_MIXED_HEAD
|All requests are sent through RPC connection, eth_subscribe is sent through WS connection, head subscription works through scheduled RPC head request mixed with WS subscription.
|RPC_REQUESTS_WITH_WS_HEAD
|All requests are sent through RPC connection, all subscriptions works through WS connection.
|===
You can specify this modes through `connector-mode` parameter in connection config.
=== Bitcoin Methods
.By default an ethereum upstream allows call to the following JSON RPC methods: