Jason Spisak wrote:
Pavlos:
And never forget the filesystem! Allows highly efficient concurrent writes, optimized caching at the kernel level, has a nice hierarchical structure and there are many tools to work with it! In situations where you have high write rates but the write operations are decoupled...
Besides session info, what types of info would be good and bad in a FS storage?
Here's a hypothetical situation: Suppose you were implementing a Slashdot style moderation system in Zope, and that furthermore, you were allowing few people to post replies on your site, but you allow all visitors to moderate promiscuously (and anonymously). Beyond the fact that this may not be a good idea, you might want to store the postings in Zope, but the moderation score on the FS, as it is likely to get overwritten A LOT (especially by moderation bots). You run the slight risk of a given moderation being overwritten, but statistically it should even out with as many 'up' moderations being discarded accidentally as 'down' ones. And you prevent Zope from thrashing with many tiny committed transactions mucking up the 'Undo' tab. HTH, Michael Bernstein.