You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are looking to track additional statistics related to the connection, with a primary focus on measuring latency.
This requires calculating the time difference between PING and PINGRESP. However, it seems unlikely that many others would have a similar need for latency measurement on the connection.
Additionally, it is not possible to simply override the PINGRESP handler, as all messages are processed within the wait_msg function. For our use case, it would be beneficial if the PINGRESP handler here were separated into its own function, allowing us to override it more easily.
I understand if you prefer not to make this change, as it introduces a modification that very few others are likely interested in. If you are interested, I can submit a PR with the changes.
The text was updated successfully, but these errors were encountered:
We are looking to track additional statistics related to the connection, with a primary focus on measuring latency.
This requires calculating the time difference between PING and PINGRESP. However, it seems unlikely that many others would have a similar need for latency measurement on the connection.
Additionally, it is not possible to simply override the PINGRESP handler, as all messages are processed within the wait_msg function. For our use case, it would be beneficial if the PINGRESP handler here were separated into its own function, allowing us to override it more easily.
I understand if you prefer not to make this change, as it introduces a modification that very few others are likely interested in. If you are interested, I can submit a PR with the changes.
The text was updated successfully, but these errors were encountered: