HTTP/2 Gateway

[CJ Ess]

I think what they are asking is to support the transport layer so that they
don't have to support both protocols on whatever endpoint they are
developing.

Maybe I'm wrong and someone has grand plans about multiplexing requests to
an upstream with http/2, but I haven't seen anyone ask for that explicitly
yet.


On Tue, Dec 15, 2015 at 4:40 AM, Valentin V. Bartenev <vbart at nginx.com>
wrote:

> On Monday 14 December 2015 18:24:01 Nicholas Capo wrote:
> > My specific use case is to support an HTTP/2 application behind a load
> > balancer (reverse proxy).
> >
> > Also as a backend LB between services that could use a long running
> HTTP/2
> > connection to do their communication.
> >
> > Places where I need an LB, but also know that both ends would /prefer/ to
> > use HTTP/2.
> >
>
> Can you name such applications that are only able to talk HTTP/2?
>
> HTTP/2 isn't a better and shiny version of HTTP, it's completely
> different transport layer with a number of disadvantages as well.
>
>   wbr, Valentin V. Bartenev
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20151215/e495b2d2/attachment.html>