- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Wed, 13 Jul 2016 09:53:02 +1000
- To: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Cc: Julian Reschke <julian.reschke@gmx.de>, Carsten Bormann <cabo@tzi.org>, Willy Tarreau <w@1wt.eu>, Yanick Rochon <yanick.rochon@gmail.com>, Phil Hunt <phil.hunt@oracle.com>, HTTP Working Group <ietf-http-wg@w3.org>
FWIW, my dislike of CBOR is strong, but I've been warming to this
notion. But I would suggest that we NOT base{64,85} anything. HTTP/2
carries octets very nicely, the only catch being 0x00, which we can
finagle around.
On 12 July 2016 at 18:22, Poul-Henning Kamp <phk@phk.freebsd.dk> wrote:
> CBOR [...] includes information that is surplus to (our) requirements
Here you have identified the core challenge, and the biggest weakness of CBOR.
Apologies for the mangled quoting, but I think that it's a very
important point to make.
Received on Tuesday, 12 July 2016 23:53:32 UTC