|
|
Post by Old Shendemiar on Feb 11, 2004 12:28:29 GMT
Anyone know a good article about principles in maintaining complex site structure with includes.
Is is better to make one documet with conditional includes or many documents with the same includes?
|
|
|
|
Post by sparrowhawk on Feb 11, 2004 12:53:12 GMT
From a security point of view, one page with a switch() statement is probably best as it hides the names of the scripts from hackers.
Also, a single script allows you to build a mini content management system quite easily.
Having said that, MU uses the opposite approach! No particular reason, just grew that way. If I were to do it over, I'd probably go for a single page.
|
|
Perun
Public Area Guest
Issa (Vis) [1:76:24]
Posts: 2,506
|
Post by Perun on Feb 11, 2004 19:28:33 GMT
I started with standard procedural approach + includes, then quickly got bored with that. Now I'm using classes, so includes are just there for class inclusion, nothing else. I'm trying to make classes as self-sufficient as possible, since PHP classes are not really OOP-compliant as one would want. But PHP still beats ASP hands down, IMHO.
|
|
|
|
Post by sparrowhawk on Feb 11, 2004 21:52:18 GMT
PHP 5 is/will be as OOP as you could possibly want.  |
|
