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

Paolo Molaro lupus@ximian.com
Thu, 19 Jun 2003 17:51:21 +0200

On 06/19/03 Ben Maurer wrote:
> On Thu, 2003-06-19 at 03:18, Paolo Molaro wrote:
> > *) the work is better than the current one (for many meanings of
> > better: faster, more maintainable, more complaint to the spec...)
> Yes, the work will be:
>       * Faster: If the XML is in a good format, a bit of web design
>         magic can actually make it faster than it is currently (right
>         now we use a table heavy design, I am trying to fix that)

The use of tables has nothing to do with the issue we were discussing.
Besides, if you're optimizing for the status pages, by the time you're
done we hope to have reduced significantly the size of those pages

>       * More maintainable: Even if we don't get our new corcompare tool,
>         this will be easier for Miguel. Right now, to update the page he
>         has to 1) boot to windows 2) run the current tool 3) transfer
>         the output to his Linux box 4) run the current make file 5)
>         transfer. With the transform on the web server he can 1) boot to
>         windows 2) run tool 3) transfer. I have talked to him, and this
>         is very important to him.

You're off-base with the priorities: the main issue is point 1, all the
rest can be automated. If the new site/tools don't eliminate step 1,
they are useless.

> Remember, by "dynamic" I do *not* mean that the files are transformed on
> each request. I am planning on caching the results. But since the
> transform is taking place on the server, I don't want to take up gobs of
> unnecessary CPU time.

And the best way to avoid that is to do the transform offline: very
simple, very effective, very reliable and very fast.


lupus@debian.org                                     debian/rules
lupus@ximian.com                             Monkeys do it better