-
Notifications
You must be signed in to change notification settings - Fork 332
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recommend RPC-based pull
event source over WebSocket-based push
event source
#4190
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are there any tests left for push
mode?
@@ -123,7 +123,7 @@ grpc_addr = 'http://127.0.0.1:9090' | |||
|
|||
# Specify the WebSocket address and port where the chain WebSocket server | |||
# listens on. Required | |||
event_source = { mode = 'push', url = 'ws://127.0.0.1:26657/websocket', batch_delay = '500ms' } | |||
event_source = { mode = 'pull', interval = '500ms', max_retries = 3 } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comment above needs update.
As discussed in the IBC meeting:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the reason we recommend pull
over push
? I think we should write something either in a new section of the Configuration section, https://hermes.informal.systems/documentation/configuration/index.html, or if this is only related to performance it can also be added directly in the performance tuning section https://hermes.informal.systems/documentation/configuration/performance.html.
|
||
# ... | ||
``` | ||
|
||
> **Caution:** The "Basic" authentication scheme sends the credentials encoded but not encrypted. | ||
> This would be completely insecure unless the exchange was over a secure connection (HTTPS/TLS). | ||
|
||
## Configuring Support for Wasm Relaying |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is the entire block removed?
Closes: #XXX
Description
PR author checklist:
unclog
.docs/
).Reviewer checklist:
Files changed
in the GitHub PR explorer.