|
From: Todd O. <to...@da...> - 2001-03-25 03:51:14
|
Geoff, your logic looks good to me. I assume $dbp means "database prefix". My only question is how will $dbp be assigned? Will there be separate config files hard coded for each site? BTW, I don't have anything left to commit; you might check on Matt's calendar rewrite though. As I was writing up my long range goals, I ran across the opposite problem that Geoff had. What if your site(s) get too large for one database server to handle? Let's assume you're using the one table approach and you have 100,000 users and 1,000 sites on a single install. I can forsee the threaded discussion groups and mailing list archives for these organizations growing VERY quickly. I think we need to code with this in mind. I'm thinking about a server for core features and most plug-ins, but a separate database server for forums and list archives and possible a third for images (although not in a database). This can be solved by connecting to separate database servers once and passing the database handler to the appropriate objects in a similar way Geoff proposed abstracting the table name. Thoughts anyone, anyone? --Todd |