Re: Re: [PyCS-devel] Re: Maybe problems with Metakit 2.4.9.3

Hi!

> If you're porting databases for PyDS, I'd love to see `DB-API2`_ used 
> so we
> can put PyDS on any [relational] database we need to. If you want a 
> more
> Pythonic abstraction to work with, SQLObject_ is nice. I must admit, 
> I've

For PyDS that actually would be the way to go, as SQLObject gives me 
some abstraction in the way I have now with Metakit. I don't know 
wether it's really the right way for PyCS, though. I think it should 
directly use DBAPI and I think it should go to a full blown SQL server, 
not SQLite (although that would stay an option because of DBAPI) 
because of the higher load on those systems. Both muensterland.org and 
pycs.net get quite a big whip of traffic every day and I think a 
separate SQL server is in order there.

Another problem with SQLite is, it only handles one writer while 
allowing multiple readers. That's the same as with Metakit (ok, you can 
have multiple database connections with one writer each, but that will 
end in file locking if I understand it's architecture correctly). One 
thing that is problematic with the current PyCS is it's blocking 
nature, as all extensions are run in the main thread. Maybe it would be 
a good idea to port over PyCS modules to TooFPy to get multiple thread 
handlers for dynamic stuff (you keep the single threaded 
highperformance medusa engine for static stuff with TooFPy!).

bye, Georg