text stringlengths 0 1.32k |
|---|
**James Snell:** We've really covered a lot of it. The big thing, I would say, is the folks are really passionate about this. We need to hear from users, we need to hear from folks that have ideas on how to implement it, or how to test, or what kind of applications they wanna build with this thing. I've had a lot of co... |
**Adam Stacoviak:** \[34:56\] What's the best way for people to reach out to you then? If it's feedback you want -- is it you, personally? Should they go to the repo, submit an issue? |
**James Snell:** Go to the repo, open issues... For the folks that really want to get it in there, pull requests are great. There's been a lot of churn in the code. I've been getting in there and just hammering away for the past two weeks... |
**Adam Stacoviak:** With a machete? |
**James Snell:** Yeah, pretty much. People have been asking... It's like, "Well, where are the two dudes, so we know where to jump in?" I was like, "I don't even know what the heck I'm gonna do tomorrow, let alone what to recommend you jumping on." But it's certain to stabilize more, and there are very distinct areas t... |
**Adam Stacoviak:** Testing performance, things like that. |
**James Snell:** Right. |
**Adam Stacoviak:** Well, we'll link up the repo in the show notes for this. James, thanks so much for... We're literally closing down Node Interactive, so thank you so much for taking the time to speak with me. It is important that we have this conversation, so I know that the Node community is gonna appreciate what y... |
**James Snell:** Right, yeah. |
**Adam Stacoviak:** Thanks, man. |
**James Snell:** Thanks! |
• Introduction to Spotlight series on Node.js |
• Interview with James Snell about H2 implementation for Node.js |
• Discussion of current state and challenges of implementing H2 in Node.js |
• Debate over whether H2 should be a module or part of Node's core |
• Importance of keeping Node's core small and focused |
• Defining what belongs in Node Core vs. separate modules |
• Importance of keeping Node Core small and focused on web fundamentals |
• URL parsing as an example of a functionality that could be moved to a separate module |
• Discussion on H2 protocol and its differences from H1, including binary framing, stateful header compression, and implications for web application design and performance |
• Security as a top priority for the next year |
• H2 protocol will be designed to be highly spec-compliant and prioritizes security over performance |
• H1 was not fully compliant with the specification, which led to several security issues |
• H2 servers will require TLS connections by default due to browser implementation requirements |
• Node's reputation as a TLS terminator is a limitation that needs improvement for better performance |
• H2 enables new extensibility models and possibilities for new kinds of protocols |
• New proposals for other layered protocols are emerging within the working group |
• WebSockets' relationship with H1 is being considered as a precedent |
• The framing model in H2 will allow for experimentation without the pain of introducing WebSockets like before |
• Potential innovations could come out of it, but require collective experience and testing |
• Criticisms of the H2P protocol include: |
• Inefficient header compression (staple header compression) |
• Repetitive headers leading to waste in transmission |
• HPAC's stateful compression model adds complexity |
• Maintaining state tables can be resource-intensive |
• Additional complexity in H2 compared to H1 |
• Flow control and prioritization in H2 |
• Impact on proxy software vendors and protocol criticism |
• Server affinity issue with H2 |
• Performance benefits of using H2 efficiently (e.g. better request handling) |
• Memory usage trade-off for increased performance |
• H2 protocol offers a significant savings of header bytes, potentially saving users money on bandwidth costs |
• The adoption of H2 requires careful consideration due to trade-offs in security and API compatibility with H1 |
• Status messages are removed in H2, which may break existing applications that rely on them |
• Designing an application specifically for H2 is necessary to take advantage of its capabilities |
• H2 is more suitable for internal server-to-server communication rather than user-facing web servers |
• The H2 project is currently being worked on by a single developer with plans to grow the team and accept open-source contributions |
• H2 protocol implementation and integration into Node.js |
• Discussion about deprecating the H1 protocol in favor of H2 |
• Decision to offer both H1 and H2 as options for developers |
• Implementation challenges and future plans for HTTP development in Node.js |
• Consideration for a module-based approach for H2 implementation |
• Discussing the size and complexity of an ecosystem |
• Need for input on code direction |
• Best ways to provide feedback and get involved (repo, open issues, pull requests) |
• Code stabilization and distinct areas needing help (tests, performance benchmarks) |
• Linking repo in show notes |
• Closing down Node Interactive |
[0.52 --> 5.72] Bandwidth for ChangeLog is provided by Fastly. Learn more at Fastly.com. |
[7.18 --> 11.14] You're listening to Spotlight, a show that takes place around big announcements, |
[11.68 --> 15.12] at conferences, in the hallways, and behind the scenes. |
[15.50 --> 19.68] It's about getting out and having meaningful conversations with real people in the community. |
[20.26 --> 23.30] It's ChangeLog in the trenches, shining our spotlight. |
[30.00 --> 36.60] Welcome to our Spotlight series titled The Future of Node, recorded at Node Interactive 2016 in Austin, Texas. |
[36.92 --> 43.82] We produce this in partnership with the Linux Foundation, the Node.js Foundation, and it's sponsored by IBM and StrongLoop. |
[44.12 --> 49.96] Check out IBM API Connect, a comprehensive solution to manage your entire API lifecycle from creation to management, |
[50.32 --> 53.08] at developer.ibm.com slash apiconnect. |
[53.20 --> 58.38] Also, check out Loopback from StrongLoop, a highly extensible, open-source Node.js framework |
[58.38 --> 64.14] that enables you to create dynamic, end-to-end REST APIs with little-to-no coding at loopback.io. |
[64.40 --> 66.84] In this episode, I talk with James Snell. |
[67.20 --> 73.56] James is a technical lead for Node at IBM and a member of Node's TSC and CTC. |
[74.14 --> 79.30] We talked about the work he's doing on Node's implementation of H2, the state of H2 in Node, |
[79.60 --> 83.98] what this new spec has to offer, and what the Node community can expect from this new protocol. |
[84.36 --> 84.86] Let's take a listen. |
[84.86 --> 88.58] So what's the state of H2 in Node? |
[88.62 --> 90.04] I know you're working on it now. |
[90.20 --> 93.90] You've recently tweeted about a prototype server. |
[93.90 --> 99.32] So the current state is just trying to figure out how it would work in Node. |
[101.24 --> 104.96] There's a lot of new things within H2. |
[105.26 --> 110.12] It's a brand-new protocol, even though it's got the HTTP semantics with the crest response headers |
[110.12 --> 110.80] and that kind of thing. |
[110.80 --> 113.64] On the wire, it's very, very different. |
[113.92 --> 116.56] So it requires a completely new implementation. |
[117.16 --> 121.02] So kind of teasing the edges of what that implementation would need to look like, how it would work, |
[121.08 --> 127.56] what the issues are, what the additional state management, what impact that's going to have on Node. |
[128.06 --> 133.14] It's trying to figure out what that impact is going to be. |
[133.14 --> 137.44] And then if we were going to put it in core, if it's something that was going to land there, |
[137.60 --> 144.32] what would that look like in terms of APIs and in terms of just kind of the performance profile and that kind of thing? |
[144.44 --> 145.32] So that's where we're at. |
[145.86 --> 149.08] We had a discussion earlier, Thomas Watson and Sam. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.