"Carl S. Gutekunst" <csg(_at_)alameth(_dot_)org> writes:
Which do you think makes more sense for encapsulating John's CDAT data,
something that looks more like BDAT (length indicator), or something that
looks more like yEnc ("quoted unprintable")?
BDAT is way cleaner if you can change the protocol. yEnc is a hack around
not being able to define a new POST or ARTICLE command in NNTP with saner
data handling and instead working around line length limits, CRLF pairing,
and dot stuffing, all of which is painful for binary data. It's way more
likely to have bugs, whereas BDAT's counted binary data is far cleaner and
easier to implement correctly.
--
Russ Allbery (eagle(_at_)eyrie(_dot_)org)
<http://www.eyrie.org/~eagle/>
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp