Skip to content

Conversation

@TingDaoK
Copy link
Contributor

@TingDaoK TingDaoK commented Jul 14, 2022

  • Add stream manager for HTTP/1
  • Add unified stream manager to handle both HTTP/1 and HTTP/2
  • Support expected protocol for unified stream manager

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@TingDaoK TingDaoK mentioned this pull request Jul 14, 2022
@TingDaoK TingDaoK changed the title New unified sm New unified stream manager Jul 14, 2022
@TingDaoK TingDaoK marked this pull request as ready for review July 14, 2022 23:23
|| connectionManagerOptions.getTlsContext() != null) && priorKnowledge) {
URI uri = connectionManagerOptions.getUri();
boolean useTls = HTTPS.equals(uri.getScheme());
if (useTls && priorKnowledge) {
Copy link
Contributor

Choose a reason for hiding this comment

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

is this java only limitation? should we check it on native side instead?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

we do check it in C. I think this is for checking the options in java so that it can throw a better exceptions directly in Java?
Looks like it was the pattern we used in the connection managers as well. https://github.com/awslabs/aws-crt-java/pull/436/changes#diff-cf32dbe053c97dc09c87d3363e5234d15462c8d60baefda59cd8c6bdcba4db6e

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