Wow, that was fast. Thanks for the replies.
My intention was originally to disable caching because I thought the
issue of how fast it could serve cached content wasn’t as interesting as
how fast it could do uncached content. I’d include a warning in the
text that actual implementations would be considerably faster due to the
presence of the cache, and possibly use memcached after the last run to
give comparison numbers.
I was going to run using 2.6.0_with-rails, since the folks I’m writing
for really get queasy around anything with a whiff of “beta” around it.
Deactivating the sidebars shouldn’t be that much of a problem.
Thanks again,
Sam
2.6.0? eek, that’s ooooold. It’s also using Rails 1.0 - 1.1 would
probably be a lot more relevant for you.
Kevin B. wrote:
2.6.0? eek, that’s ooooold.
9 days old, to be precise, according to
http://rubyforge.org/projects/typo/
It’s also the most recent release. If the developers didn’t want people
using code that old, they’d make a newer release, wouldn’t they? 
mathew
On Apr 12, 2006, at 11:03 AM, mathew wrote:
Kevin B. wrote:
2.6.0? eek, that’s ooooold.
9 days old, to be precise, according to http://rubyforge.org/
projects/typo/
Well, uh, that’s an interesting timestamp there. 2.6.0 has been out
for ages.
It’s also the most recent release. If the developers didn’t want
people
using code that old, they’d make a newer release, wouldn’t they?
Speaking as a developer, I really want to get 4.0 out the door.
Current trunk is perfectly usable, we just haven’t finished quite
everything we want in 4.0.