I had been looking to use SQLObject as the database backend for an active web framework I'm building, but have had a fresh look at Metakit, and see a lot of positives.
However, I'm unclear about some Metakit issues, and hope you might be able to enlighten me:
Memory footprint: - does Metakit load the whole DB into memory upon calling storage()? - does Metakit hold each entire view in memory?
Concurrency: - what are the better schemes for db locking, in cases where multiple clients (eg under Apache CGIs) need to write to a db? - if I'm using file locks to make it safe for multiple client writes, how severely will this impact the website performance under load (eg if being slashdotted) ? (worst case scenario - someone doing a site search)
I look forward to your comments and insights
Cheers David
--
leave this line intact so your email gets through my junk mail filter _____________________________________________ Metakit mailing list - [EMAIL PROTECTED] http://www.equi4.com/mailman/listinfo/metakit
