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

Update receiver bandwidth print to respect pf:json #402

Merged
merged 2 commits into from
Jun 1, 2018

Conversation

boushley
Copy link
Contributor

The receiver mode in stransmit did not respect the json print format
request.

@@ -161,6 +161,19 @@ void PrintSrtStats(int sid, const PerfMonType& mon)
cerr << output.str() << std::flush;
}

void PrintSrtBandwidth(double mbpsBandwidth)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please make PrintSrtBandwidth() static

Copy link
Contributor Author

@boushley boushley Jun 1, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added the static modifier. Should I do the same for PrintSrtStats? That's what I modeled this after...

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for pointing that out @boushley! I took the liberty of making the change directly on your branch since I was already looking.

The receiver mode in stransmit did not respect the json print format
request.
@boushley boushley force-pushed the fix-json-printing branch from 83fd84d to 25e1ed9 Compare June 1, 2018 02:04
@rndi rndi merged commit 64184c3 into Haivision:master Jun 1, 2018
@boushley
Copy link
Contributor Author

boushley commented Jun 1, 2018

👍

@boushley boushley deleted the fix-json-printing branch June 1, 2018 16:25
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