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

Session Proposal: HTTP/2/3 evolution #278

Closed
4 of 11 tasks
Ethan-Arrowood opened this issue May 7, 2020 · 18 comments
Closed
4 of 11 tasks

Session Proposal: HTTP/2/3 evolution #278

Ethan-Arrowood opened this issue May 7, 2020 · 18 comments
Assignees
Labels
Austin 2020 Collaborator Summit Project Working Session Track for proposals that support a specific project's needs Session Proposal A session proposal for the Collaboration Summit

Comments

@Ethan-Arrowood
Copy link

Ethan-Arrowood commented May 7, 2020

Proposal

Topic of the session

The topic of this session is to discuss the evolution of HTTP, HTTP2, and HTTP3 in Node.js. We want to invite frameworks maintains and Node.js collaborators so we can share perspectives and make progress together.

cc @nodejs/web-server-frameworks @nodejs/quic @nodejs/http @nodejs/http2

Type of the session

  • Collaborate
  • Workshop
  • Talk

Timezone of facilitator

Facilitators are in multiple different time zones. Please favor the European based ones for scheduling purposes.

Estimated duration of the session

1 hour

Follow-up / Set-up sessions (if any)

Level

  • Beginner
  • Intermediate
  • Advanced

Pre-requisite knowledge

Familiarities with the web-server-frameworks working group.

will update this section when we have relevant issues in our repo

Describe the session

This session will be a discussion on the status of http/2/3 in Node core. The main discussion points will be focussed around "whats coming next" for each of these modules. We will hear from @jasnell on how QUIC is doing. One of the other key talking points will be about adoption of http 2 and 3 in real-world scenarios. The WG has discussed this previously so it'll be great to revisit this discussion and see what we can do to better support developers.

If you have other topic ideas please feel free to comment them on this issue and we'll bring them up in the discussion.

Session facilitator(s), Github handle(s) and timezone(s)

Ethan Arrowood (@Ethan-Arrowood) - EST
Matteo Collina (@mcollina) - CEST

Additional context (optional)

I do not need to be facilitator for this if someone else is better suited. Just putting my name down because I'm more than happy to do so, and I've been facilitating the web-server-framework working group calls.


This section is for contributors handling Collaborator Summit logistics

Track

Triage

  • Track chosen
  • Scheduled

TCQ: https://tcq.app/meeting/5kWx

@benjamingr
Copy link

This looks cool, is the goal to gather feedback from framework authors and make decisions on APIs or how to push QUIC? What sort of feedback would be helpful?

(In any case I'd ping James and nodejs/quic if the goal is to get feedback to people working on http3 in Node.js and I can think of some other people in core :])

@Ethan-Arrowood
Copy link
Author

Ahh yes! I knew I forgot something. Meant to cc quic, http, and the other groups here as well.

@benjamingr and yes that is very much what we are interested in doing. We've had some conversations already during the WG calls about supporting things like QUIC. One of the main pain points we have identified is how users actually are using the http/2/3 apis being built. We hope this session would allow us to really focus on it for a whole hour and make some actionable moves to improving userland things.

@benjamingr
Copy link

Ah, I can't ping Node teams from here apparently because it's a different organization. That's an interesting result of being the OpenJS foundation but having Node in nodejs/node :]

@Ethan-Arrowood
Copy link
Author

I'll make a note to ping them through twitter/email then 😉

@mcollina
Copy link
Member

mcollina commented May 7, 2020

count me in!

@Ethan-Arrowood
Copy link
Author

@mcollina i can add you as a facilitator, what is your time zone?

@jasnell
Copy link
Contributor

jasnell commented May 7, 2020

No worries about notifying me, I spotted it ;-) ... yes I'll definitely attend and can give an update on where we are at with the implementation and current thinking around the API.

@mcollina
Copy link
Member

mcollina commented May 7, 2020

I’m in CEST.

@jorydotcom jorydotcom added the Project Working Session Track for proposals that support a specific project's needs label Jun 5, 2020
@Ethan-Arrowood
Copy link
Author

Do we know if this is happening or not, and if so when it'll be? Just looking to set aside the time to attend and give my team at work the heads-up I might be out.

@benjamingr
Copy link

@Ethan-Arrowood - it appears to be on the agenda so I'd assume so :]

@Ethan-Arrowood
Copy link
Author

I must've missed that notification. I'll make sure to set aside the time 😄 looking forward to it!

@Ethan-Arrowood
Copy link
Author

If anyone would like to have a short call prior to the conference to do a little bit of planning for this session please let me know! My schedule is flexible and can support multiple timezones.

Additionally, if you have thoughts you'd like to share but may not be able to attend please comment here and I'll do my best to include them in the sessions discussion.

@jasnell
Copy link
Contributor

jasnell commented Jun 22, 2020

When is this session?

@jorydotcom
Copy link
Collaborator

Notes from the session room

@Ethan-Arrowood do you recall if this session was recorded?

@Ethan-Arrowood
Copy link
Author

Ethan-Arrowood commented Jul 3, 2020 via email

@jorydotcom
Copy link
Collaborator

@Ethan-Arrowood great! I'll get it from Celia.

@WaleedAshraf
Copy link
Member

Closing this issue as no further action is needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Austin 2020 Collaborator Summit Project Working Session Track for proposals that support a specific project's needs Session Proposal A session proposal for the Collaboration Summit
Projects
None yet
Development

No branches or pull requests

8 participants