Ahh, thanks! That’s what I was looking for.
ChaseGilliam
cs-victor-nascimento
One question: Plug is a specific API for HTTP? That is why we will have HTTP1.1 and HTTP2 but not websockets there? If we had websockets in Plug I’d probably not need full Phoenix for API projects.
1
OvermindDL1
Correct thus far, but that is the point of Phoenix, it is just plug with more. Just like Phoenix.PubSub is another dependency, breaking it up makes it more easily maintained.
1
OvermindDL1
First major bit was just merged in. ^.^
https://github.com/elixir-plug/plug/pull/625#event-1339464289
4
OvermindDL1
Cowboy2 support merged in a bit ago now:
https://github.com/elixir-plug/plug/pull/604
As well as with a test to ensure HTTP/2 is working:
https://github.com/elixir-plug/plug/pull/623
5
ChaseGilliam
Once this is in Phoenix, I’ll be super happy to trash a lot of my workflow around JS and CSS
1
ChaseGilliam
Is anyone interested in seeing a demo of how to get http/2 working with phoenix?
I’m using webpack to split my js into chunks and I’m serving them via http/2. So far the approach looks promising. There’s functionality in webpack to split into n chunks based on size, which looks useful, but I haven’t figured out how to dynamically include assets in a phoenix template, so that part is a WIP.
1
aseigo
ChaseGilliam
Ok, I’ll see if I can write something up soon that adds something beyond basic setup.
It’s tricky at the moment because brunch doesn’t really support breaking your bundle into multiple small files, so you need to use something like webpack, or just a bunch of static files. Doing it programatically is tricky too, because I can’t figure out how to tell phoenix view to grab all files that end in .js in a particular folder and server them to page load.
1
ChaseGilliam
Ok @aseigo here it is as promised, and only 4 weeks delayed 
!
I pushed this out quickly because it had been sitting in my drafts for a few weeks, so let me know if anything seems off.
7