Add a way to construct or derive a configuration that prefers lower-latency nodes using the latency information already exposed by Node.Latency(). The original idea was to sort nodes by observed latency so callers can select faster nodes for quorum calls or other operations.
This needs a small design pass before implementation because the main question is where the feature should live. It could be a helper that returns a reordered configuration, a filtering or selection API on Configuration, or a lighter-weight utility that callers use explicitly before issuing calls. The implementation should avoid hiding mutable network measurements behind surprising implicit behavior.
A reasonable target is an explicit API that orders or selects nodes by current latency without changing the call semantics.
Add a way to construct or derive a configuration that prefers lower-latency nodes using the latency information already exposed by
Node.Latency(). The original idea was to sort nodes by observed latency so callers can select faster nodes for quorum calls or other operations.This needs a small design pass before implementation because the main question is where the feature should live. It could be a helper that returns a reordered configuration, a filtering or selection API on
Configuration, or a lighter-weight utility that callers use explicitly before issuing calls. The implementation should avoid hiding mutable network measurements behind surprising implicit behavior.A reasonable target is an explicit API that orders or selects nodes by current latency without changing the call semantics.