Re: Architecture Question

> > > I was wondering what was considered the best way to lay > > out php files. Does the Phpshop model, were all pages go to > > one file, index.php3, which calls all functions and > > templates, work best, or is it better to have several > > different pages in PHP Normal Form. I'm starting a > > application soon and was trying to figure out which way is > > best. I look foward to hearing the different opinions. I go for a master 'includes.inc' and pull everything else in from that depending on where I'm @ in the app, it seems a logical approach and I can then divide my separate includes into managable chunks i.e. html-bits.inc, html-branding.inc, sql.inc, generic_functions.inc and so on, if I'm working with a few other developers, we can farm off different bits to each bod As I said, it seems logical, but I'd also interested if this a bad method to employ regs Bealers