Sorry if this was not 100% clear. In a nutshell the app I'm making will
be available for poeple to use. My feeling is that there will be users
using shared servers, which under a stress tend to suck. The only thing
in this one I'm doing that;s new to me is having some 20 includes loaded
as I ne
He likely ment that his local server is simply fast enough that any
speed defference is unnoticeable,
but on a shared host this might make some difference.
Use include/require as you are more comfortable with it.
Rasmus Lerdorf wrote:
Is there, was there ever issue around including a lot files v
These files are parsed by the interpreter...
They are not sent to the client, so I you are thinking bandwidth I dont see how it
would affect it.
Unless they all output a bunch of data.
Of course there will be some overhead for PHP to interpret all that code.
Mike
*** REPLY SEPARATOR
> Is there, was there ever issue around including a lot files via
> include(). I am running things on a local server so it's hard to gauge.
I don't understand that comment. includes/requires are always (well
nearly anyway) local to the server regardless of where the request is
coming from. So if
i am designing a small app that obviuosly works best when I have a lot of
global files with functions, which cut down on editing.
I will likely have a main page that will contain modules and also load
all of the required includes like config etc. in total some 10 files will
be reqested.
Is the
5 matches
Mail list logo
