Feature Request: HTTP2

[jonathanong]

@indutny has done great work with https://github.com/indutny/node-spdy. would love to see this added and released soon after the specs are finalized :D

[yorkie]

+1 for http2, that would be awesome.

[haoxins]

+1

[yosuke-furukawa]

+1

[nmn]

+1, but would also add a word of caution. That HTTP2 standard isn't quite finalized, and till that time, it makes sense for node-spdy to be the canonical way to add SPDY support.

[mikeal]

what exactly is this feature request for? is it for http2 support to be added to core or just for an work necessary for better support in userland to be added to core (I'm not sure what that would be).

[alwayrun]

+1

[yorkie]

I'm guessing @jonathanong is going to refer this forward project koajs/koala and here is a discussion about http2 and spdy.

[nmn]

I think he's asking for http2 support in core.

Again, I think that's a great idea, but the time is not right yet.

[jonathanong]

yeah this is for core support, though developing it as a userland module until all the committers agree on the implementation would be okay with me too.

[mafintosh]

whats the benefit of adding this to core instead of just having it live in userland?

[nmn]

I think eventually this should land in core. Node.js was ahead of the curve with it's core http module using http 1.1 when it came out. Once http2 standard is stable, support should ideally be added to core.

I think this is a low-level, fundamental feature that deserves to be in Core.

[defunctzombie]

Not a core issue IMO. A distribution issue.

[nmn]

Probably a little early to discuss this at all I guess. I think when the time comes, the best approach will feel obvious.

[liveinjs]

+1

[dconnolly]

+1

[defunctzombie]

Just make a module.

[ghostbar]

Can't see a win on making it part of core.

[ilanbiala]

HTTP should definitely not be a module, because that's one of the main features of core. That's what makes it so easy to put together a node app, and it's an advantage node has compared to other languages that separate it into a module.

[rlidwka]

HTTP should definitely not be a module, because that's one of the main features of core.

This "main feature" in node.js is useless. For example, I never directly use neither server (I prefer express module) nor client (I use request).

Of course we need a stable and well-maintained HTTP and HTTP2 implementations, but I don't see why it should be in core.

[ilanbiala]

If it's not in core, it should still be completely controlled by io.js, which is the same as being in core in my opinion.

[algesten]

Uhm. @rlidwka express uses http https://github.com/strongloop/express/blob/master/lib/application.js#L13 so does request https://github.com/request/request/blob/master/request.js#L3

[Fishrock123]

Support for this will be inherently necessary in the future.

HTTP/2 is landing in chrome 40 soon: http://blog.chromium.org/2015/02/hello-http2-goodbye-spdy-http-is_9.html

(+1)

[indutny]

Ok, +1 from me. I'll start working on it after we'll figure out #589