Notes on embedded binary values
This commit is contained in:
parent
348cb3e2a2
commit
268afe8a40
|
@ -1395,4 +1395,11 @@ tell whether it is an open-parenthesis or not! For this reason, I've
|
|||
disallowed whitespace between a label `Value` and the open-parenthesis
|
||||
of the fields. Is this reasonable??
|
||||
|
||||
Q. Should SOH-prefixed binary values embedded in a textual representation
|
||||
be length-prefixed, too - byte strings, essentially? Also, why not
|
||||
base64 embedded binary values? The length-prefixing might help with
|
||||
being able to avoid having to care whether the embedded value is well-
|
||||
formed or not; on the other hand, it means streaming-format embeddings
|
||||
aren't possible.
|
||||
|
||||
## Notes
|
||||
|
|
Loading…
Reference in New Issue