[Mono-list] How often is the class status page updated?

Piers Haken piersh@friskit.com
Wed, 18 Jun 2003 15:56:45 -0700

Why on earth would you want to dynamically generate the status pages on
the server? Are you expecting something to change in the assmeblies
between page loads? The only time it makes sense to update the pages is
after you've built the assemblies.

Besides: your assumption that the HTML is smaller thatn the XML is in
correct. Check the sizes, there's much more information in the
corcompare-generated XML files than are presented in the HTML.

Can you explain what "doubling back" means in the context of an XSTL


> -----Original Message-----
> From: Ben Maurer [mailto:bmaurer@users.sourceforge.net]=20
> Sent: Wednesday, June 18, 2003 2:36 PM
> To: Paolo Molaro
> Cc: mono-list@lists.ximian.com
> Subject: Re: [Mono-list] How often is the class status page updated?
> On Wed, 2003-06-18 at 17:06, Paolo Molaro wrote:
> > and will continue [t]o be static
> Really? Thats not my plan! I would like to see the new format=20
> be fast and compact enough that we could do this dynamically=20
> (with a bit of
> caching) on the server. I am also thinking about giving the=20
> XML + XSLT to uplevel clients (moz and ie6), as it would take=20
> much less bandwidth and allow for us to do some other cool things.=20
> > so if he has ideas to speedup the status pages, he can=20
> apply them to=20
> > the current stuff.
> The things I would suggest involve changing the format of the=20
> xml that we output not the xslt style sheet. And I have no=20
> interest in fixing up a tool that is about to sink ;-).
> > Besides, if Ben has suggestions, he can well make them on the list.
> Well, basically, my suggestion is to make it so that the=20
> output of tool can be parsed in one forward only pass. One of=20
> the problems with XSLT and XML is that it is *very* easy to=20
> program something that requires the transformer to double=20
> back. Right now, I think ours suffers from this. Basically,=20
> the only types of select queries that should be needed to=20
> directly get values should be ones of on the attribute of the=20
> current node. For example this would be a BAD format: <class=20
> name=3D"blah">
> 	<method name=3D"blah" implemented=3D"false" />
> </class>
> Because to find out if the blah class was fully implemented,=20
> all of the children would have to be scanned.
> We don't make errors that are quite as bad as that, but if=20
> you look at the xml, there are still similar constructs.=20
> _______________________________________________
> Mono-list maillist  -  Mono-list@lists.ximian.com=20
> http://lists.ximian.com/mailman/listinfo/mono-> list