« Meanwhile, on the spam front | Main | Winter around the corner »

Was it something I typed?

Yes, I am easily amused, thanks for asking. If you're scratching your head, look at the title bar in that image.

Comments

I stopped scratching my head when I figured out moveable type has to rebuild once in awhile..right? *keeps on scratching*

Anyway, for more geek fun, I figured i'd pass on what i'm doing right now: http://www.googlism.com/

Look at the one for Bill Gates:
http://www.googlism.com/who_is/b/bill_gates/

Anyway,
Have a good one Kasia.


Look above the Movable type logo...where it says "Loading"

*best Bevis voice* "Hehe...she said hell"

Anyways...that was always kinda frustrating with MT...the whole have to rebuild thing. It gets especially frustrating at work on our info log that has almost 2000 entries.

The rebuilding is primarily to make the blog site all html (static) pages, with the exception of comment posting and trackback pages and the like. That being said it is the rare web site that would require the performance of static pages: dynamic pages with a fast database engine like mysql would handle several hundred pages per second on reasonable hardware.

So, IMHO, the static pages and site rebuilding that MT does is like swatting a fly with a Buick.

I only have about 215 entries and it takes for-ev-er to rebuild my site, and that's using a database. Is it a default for MT to look for mod_perl to use so things go naturally faster if it's available?

And I'm not asking this cuz I don't get it, I get it, don't worry ;) I just have questions, far too many, see?

MT is designed to scale to a large number of different requirements, notably not requiring a live database.

What would be really nice is if it were to just rebuild entries as needed, though, and do something like mt.cgi/archive/000123.html (emitting the cached HTML page if nothing it depends on has changed, or rebuilding it otherwise). I don't know of any current webservers which don't support PATH_INFO parameters anymore.