Skip to content
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

Probe: remove backwards-compatibility code when publishing reports #3215

Merged
merged 1 commit into from
Jun 6, 2018

Conversation

bboreham
Copy link
Collaborator

@bboreham bboreham commented Jun 5, 2018

Removed to reduce CPU and memory usage in probes.

This code was added in August 2016 so that newer probes could be used with older apps. Since then we have adopted the stance that new apps will accept reports from old probes but not vice-versa, on a version change.

@bboreham bboreham force-pushed the remove-probe-backwards-compat branch from d1801b6 to 9021ec7 Compare June 5, 2018 14:34
Removed to reduce CPU and memory usage in probes.

This code was added in August 2016 so that newer probes could be used
with older apps. Since then we have adopted the stance that new apps
will accept reports from old probes but not vice-versa, on a version
change.
@bboreham bboreham force-pushed the remove-probe-backwards-compat branch from 9021ec7 to 009af5b Compare June 5, 2018 16:47
@umamukkara
Copy link

LGTM

@bboreham
Copy link
Collaborator Author

bboreham commented Jun 6, 2018

Thanks for the review, @umamukkara

@bboreham bboreham merged commit 269c09c into master Jun 6, 2018
@bboreham bboreham deleted the remove-probe-backwards-compat branch January 13, 2020 11:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants