Hello Graham,

GF> I've tried to develop a component/service approach. I separate out
GF> database, app logic, app ui, and http services into parts, and pull them
GF> together with a "service manager" that glues them all together at
GF> startup time.

GF> The various components are initialized and plugged into a global service
GF> lookup namespace. So, the 'http' component can discover the 'publisher'
GF> and 'application' components, and bind itself to them. Sequence of
GF> initialization is important, so I specify it in the config file.

GF> It's a bit young yet, but I like the approach. I've worked almost
GF> exclusively with the Medusa publisher, but I don't see why this wouldn't
GF> work for mod_python, scgi, etc. I'd share code if anyone wants it, with
GF> a 'work-in-progress' caveat.

This sound very much like PEAK - Python Enterprise Application Kit

Niki Spahiev