-
Notifications
You must be signed in to change notification settings - Fork 28
(PCP-410) Expose the connection timings #185
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -6,8 +6,19 @@ namespace PCPClient { | |
|
|
||
| namespace lth_loc = leatherman::locale; | ||
|
|
||
| ConnectionTimings::ConnectionTimings() | ||
| : start { boost::chrono::high_resolution_clock::now() } { | ||
| // | ||
| // ConnectionTimings | ||
| // | ||
|
|
||
| void ConnectionTimings::reset() | ||
| { | ||
| start = boost::chrono::high_resolution_clock::now(); | ||
| tcp_pre_init = boost::chrono::high_resolution_clock::time_point(); | ||
| tcp_post_init = boost::chrono::high_resolution_clock::time_point(); | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. repeated line
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Probably should be
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. thanks |
||
| open = boost::chrono::high_resolution_clock::time_point(); | ||
| close = boost::chrono::high_resolution_clock::time_point(); | ||
| connection_started = false; | ||
| connection_failed = false; | ||
| } | ||
|
|
||
| ConnectionTimings::Duration_us ConnectionTimings::getTCPInterval() const { | ||
|
|
||
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 did you make this public?
Uh oh!
There was an error while loading. Please reload this page.
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.
Since the new AssociationTimings will be stored in the Connector, it makes more sense to me to allow Connector accessing directly the ConnectionTimings instead of having a copy from a Connection getter call. This is done considering that the actual user interface is provided by Connector, that does not expose the Connection instance.
No strong opinion here, I'm happy to make it private again if you think it's the case.
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.
Seems ok.