Ian, > If each application had its own configuration file and independent > existance then this shouldn't be any problem -- URLs won't be conflated > with applications, and it will only be in unusual situations where an > application will have more than one database connection. As you enter > the application you set the connection, and restore it (probably just > delete it) on the way out of the app. Anyway, this doesn't help that > much, because you can't do this now. But really everything will become > much simpler when it is possible!
We may be understanding "application" differently. In my understanding I may have a single application running for multiple clients. Therefore the single TurboGears application may need multiple databases - one per client. For simple hosting I would want a single wsgi server running an application that uses the url to partition by client with a separate database for each (so that I don't have to worry about including the client in every database key). I would assume that adding a separate application instance for each client when their usage will be small would be a big overhead (memory and management). Dave
