- From: Willy Tarreau <w@1wt.eu>
- Date: Wed, 3 Feb 2021 12:30:10 +0100
- To: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Cc: Martin Thomson <mt@lowentropy.net>, ietf-http-wg@w3.org
On Wed, Feb 03, 2021 at 10:42:17AM +0000, Poul-Henning Kamp wrote: > The problem with trailers has always been that people get hung up over the > marginal potential speedups if we allow things to "change later". I'm not sure I understand what you mean. What "marginal potential speedups" are you talking about ? > But no software in the HTTP ecosystem is prepared for things to "change > later". Well, gRPC for example is a counter example, it *wants* a trailer for the status. I think the ecosystem doesn't exploit trailers that much because trailers are not much used nor produced, but I think most implementations by now at least parse them, and that extending them a little bit to support reading a set of more optimal caching instructions wouldn't be that hard. Willy
Received on Wednesday, 3 February 2021 11:30:27 UTC