Re: AW: Big, BIG databases.

Bauer, Georg wrote:
> Yep. Metakit - especially in non-standard environments - sometimes behaves
> quite worrying. I think it would be time to start refactoring that throws
> out Metakit and pulls in something more stable. I'd gladly accept patches
> ;-)

I've started hacking on this on a couple of occasions, but it is pretty 
hard for me as an "outsider".

I really find myself itching for a two part split, where, taking the 
Weblog tool as a for-instance, there is a Post class, which can be 
loaded in several ways, and some sort of storage backing abstraction 
that would do most of what metakit does now, but it's too large a 
project for me to undertake on my own. (Particularly as it is really the 
WeblogTool I want to hack on and that's really tightly integrated.)

I keep going to do things and running up against the fact that the 
rendering and storage are so interleaved, and so far I haven't been 
successful in disentangling it yet, because I haven't come up with a 
need that justifies the time.

I've got some time coming up over the next few weeks. Maybe I'll take 
another crack at it, especially as my "don't complain unless you're 
willing to do something about it" sense is nagging me. It occurs to me 
as I type this that it might be easier to start out with a Post object 
and then work on abstracting the storage, rather than the other way 
around as I tried before.

I've got some things to attend to fir$t, but I'll hit you up for a 
subversion account sometime over the next couple of weeks, Georg. I'll 
start in a branch, of course, but it'll be easier for me if it's in 
source control the whole time. And I'll try to remember to stay 2.2 only 
:-)