[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svndiff and XML

From: Brian Behlendorf <brian_at_collab.net>
Date: 2000-10-11 22:40:50 CEST

Only a format that uses a content-length descriptor can embed arbitrary
binary data into a composite form; look at HTTP, for example. Or in MIME
- do any of the multipart/* formats allow for binary data without
encoding anyways? The ones I see always use \n-- to demark a new
segment.

Do we need to go all the way down to base64? There's got to be a more
better encoding pattern given there's only 4 chars we need to
avoid.

Maybe svndiff + gzip?

        Brian

On 11 Oct 2000, Ben Collins-Sussman wrote:
> After all your compression benchmarking, it must be frustrating to be
> forced to expand your data by a third!
>
> At first, I thought to myself, "Thank goodness this is for XML only,
> which is really only an occasional interchange format. The real DAV
> communications will someday send actual vcdiff or svndiff data over
> the wire."
>
> But now I just realized that the DAV is still HTTP messages -- does
> this mean we're stuck base64'ing *all* binary data, even in Subversion
> 1.0, forever and ever?
>
>
Received on Sat Oct 21 14:36:10 2006

This is an archived mail posted to the Subversion Dev mailing list.