Hacker News new | ask | show | jobs
by dtech 2494 days ago
> Consider as well that all JSON numbers are floating point numbers, despite the fact that floating point numbers provide absolutely nothing of value to this spec

JMAP seems to not use any float, so implementers do not need floating point logic and can just reject JSON with floats.

Aren't most email attachments base64 encoded anyway? If so, JSON not supporting binary is not really a problem.

1 comments

Converting to base64 generally increases the payload size. Being able to convert it that way is a workaround - not a solution to being able to transmit binary information.
Well yes, but all emails I've ever seen already have their binary attachments encoded as base64
I received two emails yesterday with application/octet-stream as part of the inner body, compliant with RFC2046 [0]. Having a Content-Transfer-Encoding of base64 is entirely optional.

It's the default for certain larger email hosts - that's the reason you see it frequently, but that in no way means that it is the _best_ option for a protocol that suggests it's solving the problems of the old one.

[0] https://tools.ietf.org/html/rfc2046#section-4.5.1