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

WIP: Working on HTTP2 client #2

Closed

Conversation

omarkj
Copy link

@omarkj omarkj commented Jan 12, 2016

This is an ongoing PR to work on the HTTP2 client that comes with Chatterbox.

My goals are to:

  • Clean up the API (it's pretty nice now, tho);
  • Gracefully handle failure
  • Somehow make it easy to work with multiple streams over a single connection.

For now I'm not looking to:

  • Support HTTP/1.1 downgrading

@@ -601,7 +601,7 @@ handle_info({inet_async, _ListSock, Ref, {ok, CliSocket}},
ssl ->
{ok, AcceptSocket} = ssl:ssl_accept(CliSocket, SSLOptions),
%% TODO: Erlang 18 uses ALPN
{ok, _Upgrayedd} = ssl:negotiated_next_protocol(AcceptSocket),
Copy link
Owner

Choose a reason for hiding this comment

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

IIRC this needs to be a switch based on erlang version 17/18

Copy link
Author

Choose a reason for hiding this comment

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

You are right. What is a sane way of doing that? Macro party?

Copy link
Owner

Choose a reason for hiding this comment

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

probably

@joedevivo
Copy link
Owner

Hey, take a look at what I've done in http2_client on master.

@joedevivo
Copy link
Owner

a bunch of client dev has happened since this was opened.

@joedevivo joedevivo closed this Feb 19, 2016
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