From: Alby L. <al...@th...> - 2001-06-29 11:02:33
|
Another boring yet real-life example of why someone wants to use BC: The current project I'm working on is in beta / conceptual / demo stage right now - meaning it does all that it _needs_ to do but not very well or reliably. When I rebuild it, I am planning on using BC2, and that will probably be sometime in September. So here's the deal: The server will host anywhere from 3-100 sites that won't be used very often individually, but the server itself will have a decent amount of traffic overall allowing me to install so many different sites on a single machine. In addition, each site will have its own db instance - I am curious to see how this pans out. Each site will be almost identical in structure and functionality, with maybe a 10% variation between each site instance. So, my goal is to obviously re-use as much code as possible for each site, allowing them to share different modules, but also have an easy way of administering the differences between each site. Ok this site is using this set of interface components, ah - this site doesn't use the common module for handling these objects, but the specialized one I had to build for their unique situation, this db has this extra table cell... OK I've got a new site to build let me click this button and then change the preferences so that I can designate specialized modules and db characteristics. I know this is way too specific to be of design use for BC in general, but I thought it might help in considering some type of administration solution, which I am going to start conceptualizing today and next week. Come September BC2 will probably have all the kinks rolled out and I would be psyched to contribute some administration stuff to the platform. Hopefully by that time my php skills will be up to par. :?/ [ Duh, what does $this->mean? ] Alby Lash al...@th... |