Skip to content

Remove the client::conn combined-version types #2961

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

Conversation

Michael-J-Ward
Copy link
Contributor

@Michael-J-Ward Michael-J-Ward commented Aug 24, 2022

Resolves #2960

@seanmonstar ready to review, as I require your advice on the last item anyway

TODO:

  • How to handle http1::Connection::poll_without_shutdown
  • Fix failing tests
  • Cleaner http protocol specification in test
  • how to address readiness in doc for client::conn module
  • ffi::conn

See hyperium#2960
"""
The public client API for 1.0 will be the version-specific types at client::conn::{http1, http2}. The combined version may exist in hyper-util, but at least it should be removed from hyper proper. Doing so isn't particularly complex, but it will mean fixing up all the tests.
"""
@Michael-J-Ward Michael-J-Ward force-pushed the remove-combined-client-conn-types branch from 6a4a4e8 to cd6f288 Compare August 24, 2022 19:49
self.h2_tx.is_extended_connect_protocol_enabled()
}
}
// impl<B> ClientTask<B>
Copy link
Member

Choose a reason for hiding this comment

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

Is this no longer needed? I think it's how HTTP/2 does it's websocket upgrades, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

conn::http2::ClientTask is not public, and the only existing public call site is here.

ProtoClient::H2 { h2 } => h2.is_extended_connect_protocol_enabled(),

Copy link
Member

Choose a reason for hiding this comment

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

Oh I see, so probably something to add back to the http2::Connection type.

@Michael-J-Ward
Copy link
Contributor Author

Also - I apologize for just now seeing thee Commit Guidelines

Should I wait until after review to rebase and squash them all into a single commit?

This seems like the cleanes we can do without introducing a new trait or util.
@seanmonstar
Copy link
Member

I apologize for just now seeing thee Commit Guidelines

Not a problem at all! Also note here in PULL_REQUESTS:

If your message doesn't perfectly match the guidelines, do not worry! The person that eventually merges can easily fixup the message at that time.

@seanmonstar
Copy link
Member

I've rebased this and started finishing the last bit in #2987.

@seanmonstar
Copy link
Member

Finished in #2987, thanks so much!

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.

Remove the client::conn combined-version types
2 participants