Upgrading the Transport layer

[vishnu667]

Is it possible to upgrade from HTTP to SPDY / HTTP 2 for transport  of BID Requests between exchanges.

[lpgauth]

I'm not aware of anyone in the industry doing SPDY / HTTP2 for BidRequests...

[drjbutler]

OpenRTB requires HTTP support minimally, but does not preclude exchanges
and their bidders from using other transports. This is similar to
requiring JSON for representation minimally, but allowing any other
protocols (e.g., Avro, protobufs, etc.) that the parties wish to support.

:JB

On Tue, Jun 2, 2015 at 1:49 PM, Louis-Philippe Gauthier <
notifications@github.com> wrote:

I'm not aware of anyone in the industry doing SPDY / HTTP2 for
BidRequests...

—
Reply to this email directly or view it on GitHub
#18 (comment).

James M. Butler, Ph.D.* | SVP Technology
*millennial media
Mobile: 617.834.2125
Email: jbutler@millennialmedia.com
Web: www.millennialmedia.com
Twitter: @millennialmedia
Facebook: Facebook/millennialmedia

[jpathak]

From the OpenRTB2.3 spec, one of the ways indicated to improve connection performance is to use connection Keep-Alive. However it's not clear whether this avoids HOL blocking, is there any evidence of that happening in practice ?

[manigandham]

@jpathak

Connection Keep-Alive is only used to keep the TCP connection itself from closing after every request. This greatly reduces the overhead and is pretty much on by default (or should be) these days.

This has nothing to do with the actual requests themselves and multiple requests can travel over the same connection, however HTTP/1.1 has no capabilities to overcome head-of-line blocking. There is HTTP pipelining which allows for sending several requests without waiting for each response immediately but this has varying support, tends to cause more problems than it solves, and it doesn't overcome HOL blocking either.

SPDY and HTTP/2 solve the HOL blocking issue by creating multiple streams within each connection that can support requests in parallel.

[jpathak]

Thanks @manigandham!