Hi, My assumption is that turbogears may be used a lot for applications like those from 37Signals. ie a relatively small application with many clients using it whose data needs to be kept entirely separate.
How would you partition these in TurboGears? The goal is a single application instance running lots of clients. Each client should have entirely separate data and security. For example how would I code in turbogears so that mydomain.org/clientA/applicationurl uses a separate database (and separate identitifcation/permissions) from mydomain.org/clientB/applicationurl Of course I would then want mydomain.org/signup etc to be the code that creates client instances etc. It seems to me that this question has a number of implications for the identification and permission discussions underway. I suspect that the code in 20MinuteWiki for Friendlier URL's will be part of the solution. However, if I am right that this is a common need for turbogears then it would be worth documenting and providing simple support for. Thanks Dave
