I started playing around with HTTP/2, seeing as all major browsers already support it or are going to support it very soon. It makes a lot of things easier with sending multiple files to the client so could possibly make file injections easier/faster.
There's a great module for that, https://github.com/molnarg/node-http2, which seems to be backwards compatible with node's HTTP module and supports old browsers/clients as well.
What do you think?
Globegitter
All 31 comments
@Globegitter looks great!
We don't do anything fancy with server atm, so I imagine this could be just a drop-in replacement.
shakyShane
on 18 Aug 2015
I'm really glad if Node itself has HTTP/2 support, and it's discussed in https://github.com/nodejs/NG/issues/8.
shinnn
on 18 Aug 2015
+1 - would really love to see HTTP/2 support. Sounds like it could be really easy by using node-http2 as noted by @Globegitter
ghost
on 28 Sep 2015
:+1:
bmayen
on 25 Oct 2015
:+1:
christophehurpeau
on 22 Nov 2015
+1
frederikschubert
on 12 Jan 2016
:+1:
SuperMartas
on 30 Jan 2016
+1
Webjin
on 12 Feb 2016
+1
nmocruz
on 14 Feb 2016
+1
OlsonDev
on 15 Feb 2016
+1
anzeznidarsic
on 8 Mar 2016
+1
shintonik
on 9 Mar 2016
Serving many many files in develop this would save me A LOT of time
Slumber86
on 11 Mar 2016
Any updates? :D
Itrulia
on 15 Mar 2016
+1
zakjan
on 14 Apr 2016
@zakjan Please use reactions now, instead of +1 comments.
glen-84
on 14 Apr 2016
+1
artdias90
on 12 May 2016
Progress on this one?
amitev
on 21 Jun 2016
Any word on this? It would really help given that I'm using System.js and it's making tons of XHR requests.
ghost
on 29 Jun 2016
The only hold up here is the fact I've never used, or even played around with any HTTP2 implementations yet.
If someone wants to send a PR with changes to https://github.com/BrowserSync/browser-sync/blob/master/lib/server/utils.js#L34-L47 I'd be more than happy to merge it.
shakyShane
on 29 Jun 2016
@shakyShane I will try my best to open pull request with HTTP/2 today. From my understanding, we just need to generate a key and certificate and add it to an options object when using the http2.createServer function. I've already identified where it's being used (utils.js).
ghost
on 29 Jun 2016
@lgdexter There is a dummy default certificate for HTTPS, you can use the same for HTTP2.
zakjan
on 29 Jun 2016
+1
Would really love to be able to test my app's loading performance in development in browser-sync in both http and http/2!
m-andrew-albright
on 1 Jul 2016
For the love of god, please stop commenting just +1, just use the emoji reactions please
Itrulia
on 19 Jul 2016
I have got http2 working with express and to be honest it was actually slower serving 1000 javascript files than over regular http. Am hugely dissapointed by this.
el-davo
on 19 Jul 2016
@el-davo Is your app an SPA? What dependency loading library do you use?
amitev
on 20 Jul 2016
Yes I am using angularjs with systemjs and jspm. The http2 library's is node-http2 with connect server
el-davo
on 20 Jul 2016
@el-davo To gain the performance of http2 you can try the depcache functionality of jspm
amitev
on 20 Jul 2016
Thanks! I will give that a go today and report back
el-davo
on 20 Jul 2016
Just tried it there. That method shaves about 3 seconds roughly off loading time. thanks @amitev . Every little helps :). In case anyone wants to try it heres the server am using
var connect = require('connect');
var app = connect();
var fs = require('fs');
var serveStatic = require('serve-static');
require('events').EventEmitter.prototype._maxListeners = 1000000;
app.use('/', serveStatic(__dirname + '/'));
var options = {
key: fs.readFileSync('./gulp/localhost.key'),
cert: fs.readFileSync('./gulp/localhost.crt')
};
require('http2').createServer(options, app).listen(8001);
+1
avilde
on 2 Apr 2018
Related issues
Mil00Z
路
3Comments
ronilaukkarinen
路
4Comments
sedubois
路
3Comments
demisx
路
4Comments
ilianaza
路
4Comments
Most helpful comment
For the love of god, please stop commenting just +1, just use the emoji reactions please