> -----Original Message-----
> From: Mark Nutter [SMTP:mnutter@fore.com]
> Sent: Thursday, September 23, 1999 6:34 AM
> To: Blair Murri; xml-dev@ic.ac.uk
> Subject: RE: RFC: Attributes and XML-RPC
>
> Doh! "Code in haste, debug in leisure." Ok, here are the corrected
> results:
>
> $ ./make.pl
> $ ls -l
> total 14206
> -rw-rw-r-- 1 mnutter mnutter 5811846 Sep 23 08:28 attrib.xml
> -rw-rw-r-- 1 mnutter mnutter 8672170 Sep 23 08:28 child.xml
> -rwxr-xr-x 1 mnutter mnutter 999 Sep 23 08:26 make.pl
> -rwxr-xr-x 1 mnutter mnutter 976 Sep 22 13:16 make.pl~
> $ gzip attrib.xml
> $ gzip child.xml
> $ ls -l
> total 1332
> -rw-rw-r-- 1 mnutter mnutter 670757 Sep 23 08:28 attrib.xml.gz
> -rw-rw-r-- 1 mnutter mnutter 681080 Sep 23 08:28 child.xml.gz
> -rwxr-xr-x 1 mnutter mnutter 999 Sep 23 08:26 make.pl
> -rwxr-xr-x 1 mnutter mnutter 976 Sep 22 13:16 make.pl~
>
> So child.xml.gz is slightly larger than attrib.xml.gz (about 1.5%,
> assuming my math isn't as bad as my coding).
>
> That is what I would have expected. But, performance may be more
than
> network transport. I've got an app, where, for convenience, I have
> wrapped MS's IE 5 MSXML parser, and I found a significant difference
in
> speed by placing stuff that there was only one of as an attribute
instead
> of a child element. I don't know why yet, but the attributes where
faster
> (I don't know if that was "recording" speed or "retrieval" speed) than
the
> child elements using just that one parser. Of course, your mileage
may
> vary.
>
Blair L. Murri
Sr. Programmer/etc.
Wavo Corporation