top | item 46135920 (no title) gfody | 2 months ago I wonder too, for a DNS query do you ever need keepalive or chunked encoding? HTTP/1.0 seems appropriate and http2 seems overkill discuss order hn newest bawolff|2 months ago DNS seems like exactly the scenario where you would want http2 (or http1.1 pipelining but nobody supports that). You need to make a bunch of dns requests at once, and dont want to have to wait a roundtrip to make the next one. gfody|2 months ago ok multiple requests makes sense for keepalive (or just support a "batch" query, it's http already why adhere so tightly to the udp protocol)http/1.0 w/keepalive is common (amazon s3 for example) perfectly suitable simple protocol for this load replies (1)
bawolff|2 months ago DNS seems like exactly the scenario where you would want http2 (or http1.1 pipelining but nobody supports that). You need to make a bunch of dns requests at once, and dont want to have to wait a roundtrip to make the next one. gfody|2 months ago ok multiple requests makes sense for keepalive (or just support a "batch" query, it's http already why adhere so tightly to the udp protocol)http/1.0 w/keepalive is common (amazon s3 for example) perfectly suitable simple protocol for this load replies (1)
gfody|2 months ago ok multiple requests makes sense for keepalive (or just support a "batch" query, it's http already why adhere so tightly to the udp protocol)http/1.0 w/keepalive is common (amazon s3 for example) perfectly suitable simple protocol for this load replies (1)
bawolff|2 months ago
gfody|2 months ago
http/1.0 w/keepalive is common (amazon s3 for example) perfectly suitable simple protocol for this