<story><title>HTTP/2 interop pains</title><url>http://daniel.haxx.se/blog/2014/09/02/http2-interop-pains/</url><text></text></story><parent_chain><item><author>skrebbel</author><text>Is this a mistake or Google trying to force the standards process in their favour? Users seem to be blaming Firefox, not Google.</text></item></parent_chain><comment><author>josteink</author><text>&amp;gt; Is this a mistake or Google trying to force the standards process in their favour? Users seem to be blaming Firefox, not Google.&lt;p&gt;Given Google&amp;#x27;s history around this whole HTTP&amp;#x2F;2.0 shenanigans, I see little reason to see anything in their favour.&lt;p&gt;They are probably gambling that Firefox will fold (like they forced them to with DRM) so that once again, they can have it their way internet-wide without having to wait for annoying things like feedback from others and standards-committees and such.&lt;p&gt;They will probably win.</text></comment>
<story><title>HTTP/2 interop pains</title><url>http://daniel.haxx.se/blog/2014/09/02/http2-interop-pains/</url><text></text></story><parent_chain><item><author>skrebbel</author><text>Is this a mistake or Google trying to force the standards process in their favour? Users seem to be blaming Firefox, not Google.</text></item></parent_chain><comment><author>bagder</author><text>This doesn&amp;#x27;t drive the standards process in any particular direction, this is just a broken implementation that doesn&amp;#x27;t adhere to the current standard draft!</text></comment>