Allow more granular configuration of Hermes modes of operation #1518
Labels
I: documentation
Internal: improvements or additions to documentation
O: new-feature
Objective: cause to add a new feature or support
O: usability
Objective: cause to improve the user experience (UX) and ease using the product
Milestone
Crate
relayer
Summary
Allow more granular configuration of hermes client operation.
[cc @mankenavenkatesh]
Problem Definition
[Principal problem is described in #1489. This issue is a first step over one track towards fixing #1489. There will be others, e.g. migration to async, that will deal with performance.]
Proposal
Allow the user to specify at a lower granularity the mode of operation for a given instance. For this issue we want to be able to specify if client workers should run misbehaviour and/or periodic client refresh.
After an initial discussion with @romac and @adizere, the proposal here is that we take this opportunity and remove
strategy
and add new configuration sectionmode
(or something else). We also add a clients and packets sections to the configuration.Ideally the config will be changed to something like:
Acceptance Criteria
Ability to disable client misbehavior.
Ability to not clear packets on start.
For Admin Use
The text was updated successfully, but these errors were encountered: