Re: [PROPOSAL] Drop XML from .svn/entries

Peter N. Lundblad wrote:
> Hi,
>
> "Just For Fun", I experimented with replacing our current XML-based
> .svn/entries syntax with a line-based, |-separated syntax. It
> actually turns out that there is some overhead associated with using
> XML, but it is not extreme overhead.
>
> To get some idea how much overhead there actually is, I tested
> something that might be considered as a "typical work cycle". I used
> the following one-liner:

...

> If we want this, we should do it before 1.4, since we already have WC
> format upgrades.
>
> Opinions?

Why not look at YAML?

"YAML(tm) (rhymes with "camel") is a straightforward machine parsable data
serialization format designed for human readability and interaction with
scripting languages such as Perl and Python. YAML is optimized for data
serialization, configuration settings, log files, Internet messaging and
filtering. YAML(tm) is a balance of the following design goals.

# YAML documents are very readable by humans.
# YAML interacts well with scripting languages.
# YAML uses host languages' native data structures.
# YAML has a consistent information model.
# YAML enables stream-based processing.
# YAML is expressive and extensible.
# YAML is easy to implement.

It's already got implementations in most languages (Python, Ruby, Java, Perl)
and I think it's got less overhead then XML.

It would be interesting to see speed tests.

Regards,
Blair

-- 
Blair Zajac, Ph.D.
<blair@orcaware.com>
Subversion training, consulting and support
http://www.orcaware.com/svn/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org