Blogging Roller

From the Roller-dev list:

Lance: Castor is *supposed* to be caching objects for us so that we don't need to make repeated calls to the database. I suspect the way we are using Castor may not be optimal, though I really don't know enough to suggest improvements.

Webapps seem to cause problems for O/R frameworks. In an O/R framework, things seem to work properly only inside of a O/R "transaction" or "session." In a webapp, you get an object from the database in one session, close that session, allow the user to modify the object in an HTML form, then start another session to update the object in the database. Castor calls this a "long transaction." I wonder how these long transactions effect Castor's ability to cache efficiently.

I've known about this Google buys Pyra thing since Saturday night, but it seems like everybody I know is forwarding me articles about it from MSNBC, CNN Money, and other mainstream news sources. These people are blogmuggles, they don't read my weblog and don't have their own weblogs, but they can clearly see that Google buying Pyra makes this The Year That Punk Broke for blogging. Damn, that was 12 years ago. Anyhow... I'm gonna go with that analogy. I'm hoping that Rollerville is going to be the next Seattle and Roller is going to be the next Superchunk, but I'm not holding my breath.