Paul Vixie <[email protected]> wrote: > > any HTTP initiator who wants out of order response processing will have > to negotiate for it (see mogul's 2001 RID draft) and will then have new > responsibilities for matching up the out of order HTTP responses with > then-outstanding HTTP requests.
The current way to deal with out-of-order responses and head-of-line blocking in HTTP is HTTP/2. If you do DNS over HTTP then there has to be an exact correspondence between HTTP requests and responses and DNS requests and responses - anything else would be madness. This implies that DNS over HTTP/1 only supports in-order pipelined queries and responses in each connection; to avoid head-of-line blocking you need either multiple connections or HTTP/2. Tony. -- f.anthony.n.finch <[email protected]> http://dotat.at/ Humber, Thames, Dover: Southwest 6 to gale 8, occasionally severe gale 9. Rough or very rough. Rain or showers. Good, occasionally poor. _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
