[Mono-list] CorCompare XML ready

Piers Haken piersh@friskit.com
Tue, 26 Feb 2002 06:21:52 -0800

Good idea, although I'd like to hold off doing this for a little while
to prevent my brain from exploding (I like long variable names, me ;-) I
do realise not all of us have huge bandwidth.

I still think using HTTP compress is the way to go for this since we'd
get a 95% reduction right off the bat. Miguel, do you know if it's
possible to configure this on the site?


-----Original Message-----
From: Warren Schrey [mailto:warren@elven.ca] 
Sent: Tuesday, February 26, 2002 4:40 AM
To: mono-list@ximian.com
Subject: Re: [Mono-list] CorCompare XML ready

Hi Piers,

> Yeah the resulting file is a little large. I'm not sure about the best

> way to split it up, maybe we could have the corcompare tool or the 
> deploy script generate separate XML files and do it that way. 
> Alternatively we could just use HTTP compression - it compresses down 
> to about 15K!

This looks really great, Piers!  I have a suggestion for making the size
a bit smaller... shorten the class and image-file names as much as
possible. Just by doing this with the resulting HTML, I was able to save
about 50kb off of the resulting file, or about 20%.  Also, to help
performance a bit, you may want to initially have the tree closed at the
namespace level.


Mono-list maillist  -  Mono-list@ximian.com