Execution time!!!!!!
Big files if not well developed = large exec time meaning server timeouts.
small files = less timeouts and better debugging and modularity which ALWAYS
better. Modularity allows you to plug in and pull out pages with out
rendering you whole site unusable.
Of course you can have a few big files and some small files with it, depends
on what the big files do, Classes and common functions can be grouped
together.
""FredrikAT"" <[EMAIL PROTECTED]> wrote in message
99o8pm$480$[EMAIL PROTECTED]">news:99o8pm$480$[EMAIL PROTECTED]...
> Hi!
>
> What do you think is best..:
> - have alot of small .php (files)?
> - or a few big?
>
> What's good & bad with these solutions?!
>
> ---------------------------------
> Fredrik A. Takle
> Bergen, Norway
> [EMAIL PROTECTED]
>
>
>
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> To contact the list administrators, e-mail: [EMAIL PROTECTED]
>
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
