RFC: change revision serialiser

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Collins wrote:
> So, thinking about serialisers, it seems trivial to change the revision
> serialiser to something with less overhead than xml; use use utf8, so
> surely there is a simple fast utf8 format we can use (perhaps RIO?), we
> could put that into a development format pretty easily...
> 
> -Rob

Back in the day... rio isn't faster than xml. I think it was faster at some
bits (writing) but not faster at others (reading, IIRC).

We really have a quite tweaked system for xml right now, such that at least
with pure-python it is hard to beat.

The main reason I can see with going away from XML is to write partial
documents, that aren't really XML unless you put them all together.

RIO also has issue with taking a RIO stanza and putting it into another one
(it likes to double-encode or double-decode the inner stanza).

It certainly isn't hard to drop something into a new format. I would certainly
also recommend one that splits on newline more. At least, it would help our
line-based delta compression. (certainly if your inventory suggestion is
getting rid of that...)

John
=:->


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIo6sYJdeBCYSNAAMRAo/gAJsFqENzTEGn8gYLhyV5b+EIV4uX7QCfYzVd
iGkG2+Nm+T5ewgVI0Wa0dCc=
=Srgp
-----END PGP SIGNATURE-----