[Mono-list] How often is the class status page updated?
Thu, 19 Jun 2003 11:17:46 -0500
I think the point is that there is a line that you draw with regards to
dynamically generated content. You wouldn't pull an image from a
database, it doesn't make sense. There is a point where the cost exceeds
If you have to boot into windows to get a new xml file regardless, your
source data is not going to change that often. And it definitely will
not change without you knowing it. Given this, it makes much more sense
to statically generate that page, or at most send the XML/XSLT to
capable clients. There is too much overhead for too little (if any) gain
to contemplate rendering it dynamically, even if it is cached.
Forums should be dynamic... Content is added randomly.
News feeds should be dynamic, the content is added to frequently.
eBusiness sites should be dynamic, the prices need to be centralized.
Corlib comparisons? Let's face it, the corlib doesn't change often
enough to warrant being dynamic.
Just my $0.02
From: Ben Maurer [mailto:email@example.com]=20
Sent: Thursday, June 19, 2003 11:01 AM
To: Paolo Molaro
Subject: Re: [Mono-list] How often is the class status page updated?
On Thu, 2003-06-19 at 11:51, Paolo Molaro wrote:
> On 06/19/03 Ben Maurer wrote:
> > * More maintainable: Even if we don't get our new corcompare
> > this will be easier for Miguel. Right now, to update the
> > has to 1) boot to windows 2) run the current tool 3)
> > the output to his Linux box 4) run the current make file 5)
> > transfer. With the transform on the web server he can 1)
> > windows 2) run tool 3) transfer. I have talked to him, and
> > is very important to him.
> You're off-base with the priorities: the main issue is point 1, all
> rest can be automated.
I talked with Miguel about this. He said to me that he does not mind the
booting into windows part as much as he minds the requirement to
transfer stuff between Linux and Windows.
> > But since the
> > transform is taking place on the server, I don't want to take up
> > 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.
Right now, we generate *all* of our content statically. So using your
argument we don't even need an asp.net site.
Mono-list maillist - Monofirstname.lastname@example.org