Re: HTTP/2 and Websockets

Sadly, since it was something that a few of us in the WG were pushing for,
as it would have allowed intermediaries without knowledge of protocols to
do what was right for them.
That is why I truly hope that the WS extension happens (and quickly)-- I'd
love to see loadbalancers relieved of having to introspect into the data
further than the HTTP2 frame layer in order to figure out how to deal with
it reasonably.
-=R

On Tue, Nov 25, 2014 at 1:17 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 25 November 2014 at 11:55, Jason Greene <jason.greene@redhat.com>
> wrote:
> >
> > What is the benefit to preventing reframing? The negative of such a
> restriction is that intermediaries will be unable to utilize their
> knowledge of their network topology to improve performance.
>
>
> It would appear that Yukata and Andy want to use HTTP/2 frame
> boundaries as the basis for WS frame boundaries.  That implies that
> you need to prevent blind reframing.  Since reframing is an inherent
> part of HTTP/2, I note that this would be unwise.  (And for more than
> just the reasons you describe.)
>
>