Opinions on single file vs. multiple file scripts

[VooDooRT]

I'm designing version 2.0 of my ClanTEK scripts, and I was wanting to get some personal opinions from you guys about something.

Currently, ClanTEK is about 100 files that each get called when something happens around the script. Like, if someone wants to demtoe a member, it will call demote.php. When that form is posted, it'll call on demote_set.php. What I started to do now, with version 2.0, is create ONE master file along side of the functions file that EVERYTHING runs from. Basically, if an action is called, it'll call that action and ignore the rest of the file. i.e.;

if ($action =='1'){
//perform an action or post a form
}
if ($action =='2'){
//perform something else, and so on....
}

Anyway, I'm looking for opinions on doing such a thing. Will be kill the servers bandwidth, or will it help it? Only calling one larger file, yet smaller than the whole of 100 plus files, as opposed to calling 100 smaller files, each with repetitive code for logging in, ipban functions, header functions, and foot functions.

Opinions?

[trooper]

Your best bet is to group all code that belongs to the same "functionality" into the same page.

E.G everything to do with logging in / out to be in the same page.
Not only will it make it easier to maintain but also better for your sanity.

You may find that you are using the same snippet of code in lots of different pages -> (e.g mysql_query(whatever)), if this is the case consider writing functions to do the job (simply pass the correct parameters.

HTH

GM