HTTP 2.0 will require changes to servers for it to work properly, it will also require that developers learn a bit more about the pipeline or rely on some vendor to implement the "smarts" for them.
Asset Bundling on the other hand will provide a quick and easy transition for most development communities. Compress everything, update your ref's and wait for the browsers to catch up, or for your server dev team to work out push. You could still push your asset bundle with HTTP 2.0 and achieve basically the same results as if you bundled all the assets and sent them down the pipe with HTTP 2.0. I don't see them as foe's or alternatives to one another. Quite to the opposite, they seem to compliment each other quite well. On Fri, Oct 11, 2013 at 8:51 AM, Russell Leggett <russell.legg...@gmail.com>wrote: > > Not sure if this changes anything, carry on. >> >> Server push is happening as part of HTTP 2.0. Do you have a use case in >> which it's insufficient? >> >> > Not sure if this was directed at me or Jorge, but in case it was directed > at me, I wasn't actually advocating for this anymore, simply acting as a > historian. I have a solution that works fine for me right now, and I'm > content to wait HTTP 2.0 or whatever the next step is. > > - Russ > > > _______________________________________________ > es-discuss mailing list > es-discuss@mozilla.org > https://mail.mozilla.org/listinfo/es-discuss > >
_______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
