David M Johnson wrote:
On May 3, 2006, at 4:49 PM, Allen Gilliland wrote:
To put it another way, if the urls work fine without the file
extensions when why should we add them?
I think static blog generation is the only reason to use them.
If an extension affects Google (or other) searches (as John H suggests),
then that would a big reason. Bloggers want their stuff to be found and
read. My personal blog is on Blogger (which puts .html on the
permalinks) and I've been amazed at the search engine placement I've
gotten for some entries. (Hopefully Google isn't favoring their own
software)
Conventional wisdom seems to be that, in order to scale up to hundreds
of thousands or millions of blogs, we'll have go static. I'd hate that
because I love the dynamic nature of Roller. Maybe conventional wisdom
is wrong and maybe I'm worried about a problem we'll never have to solve.
The conventional wisdom may be outdated. I don't claim to know the
details, but with Dual, Dual-Processor 1U 64-bit becoming "entry level"
and RAM at about $100 per GB, the approach of cached dynamically
generated content should be able to keep up.
I recently converted a project to use Servlet-based delivery of static
content that had been served with Apache httpd after years of avoiding
that for performance reasons. When we actually ran benchmarks, the
extra CPU used by the JVM vs. native Apache wasn't a real factor.
The last major release of MovableType added more dynamic features (via
PHP) and WordPress is fully dynamic (I believe) and seems to be doing
well and being used for some large scale deployments.
Are there any specific and relevant studies or analysis available?
-- Sean
