Well if you really want to do it the perfect way, I would recommend
using only one PHP file to generate the whole site. Or if you like, have
one file with all the functions.
You should also read into classess and create most of the functions
as classess.
To do the error handling there are many wa
Hello Travis,
Friday, May 7, 2004, 7:06:03 PM, you wrote:
TL> Hi Richard,
TL> Just curious...how do you do your profiling?
Zend IDE.
View the page in IE, click the Profile button, analyse the pretty
pie-charts and graphs and stack trace until I see where the bottle
necks are :)
--
Best regard
Hi Richard,
Just curious...how do you do your profiling?
cheers,
Travis
Richard Davey wrote:
Hello Ryan,
Friday, May 7, 2004, 4:51:45 PM, you wrote:
RA> Nearly all programs can be written in *one* very large .php file but just
RA> thinking of going back in to make changes 3 months down the ro
On Fri, 2004-05-07 at 12:00, Richard Davey wrote:
> Hello Ryan,
>
> Friday, May 7, 2004, 4:51:45 PM, you wrote:
>
> RA> Nearly all programs can be written in *one* very large .php file but just
> RA> thinking of going back in to make changes 3 months down the road would be a
> RA> nightmare.
>
>
Ryan, et al --
...and then Ryan A said...
%
%
% On 5/7/2004 5:47:47 PM, Jay Blanchard ([EMAIL PROTECTED])
% wrote:
[snip]
Did you realize that you quoted Jay's quote of Paul's original note but
then snipped off Jay's comment? :-)
...
% If you are thinking only of performance this wont matter
Hello Ryan,
Friday, May 7, 2004, 4:51:45 PM, you wrote:
RA> Nearly all programs can be written in *one* very large .php file but just
RA> thinking of going back in to make changes 3 months down the road would be a
RA> nightmare.
I was just looking at this the other day - I had a local site runni
Ok, thanks. I didn't think it would make a difference. And I agree,
splitting things up makes things a lot easier.
Thanks!
From: "Ryan A" <[EMAIL PROTECTED]>
Reply-To: "Ryan A" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: RE: [PHP] PHP Websi
On 5/7/2004 5:47:47 PM, Jay Blanchard ([EMAIL PROTECTED])
wrote:
> [snip]
> I have a question regarding website design with PHP. Is it better to
> have a
> single PHP script produce different content or have a separate PHP
> script
> for every action.
>
> For example, if an error occurs, should I
[snip]
I have a question regarding website design with PHP. Is it better to
have a
single PHP script produce different content or have a separate PHP
script
for every action.
For example, if an error occurs, should I have the same PHP script
produce
an error page or have a separate PHP script
Hi all,
I have a question regarding website design with PHP. Is it better to have a
single PHP script produce different content or have a separate PHP script
for every action.
For example, if an error occurs, should I have the same PHP script produce
an error page or have a separate PHP scrip
On Thu, Feb 05, 2004 at 05:42:54PM -0500, joel boonstra wrote:
> # ini_set():
> ini_set('include_path', "{$_SERVER['DOCUMENT_ROOT']}:.");
Replying to myself, it appears that PHP >= 4.3.0 has a family of
functions specifically for tweaking include_path:
http://www.php.net/manual/en/function
On Thu, Feb 05, 2004 at 04:35:14PM -0600, John Nichel wrote:
> And if document root is different from include path? What if the
> include path is outside of document root? You CANNOT rely on
> include_path to accomplish this.
Sorry, I should have been more specific.
I was implying that you w
joel boonstra wrote:
On Thu, Feb 05, 2004 at 09:48:22PM +, Stuart wrote:
Eric Gorr wrote:
A solution I found was in dirA/index.php, to chdir( ".." ); before
the require_once, which moves the current directory to SiteRootDir and
allows otherfuncs.php to be found ... is this the best way to s
On Thu, Feb 05, 2004 at 09:48:22PM +, Stuart wrote:
> Eric Gorr wrote:
> >A solution I found was in dirA/index.php, to chdir( ".." ); before
> >the require_once, which moves the current directory to SiteRootDir and
> >allows otherfuncs.php to be found ... is this the best way to solve this
>
Eric Gorr wrote:
A solution I found was in dirA/index.php, to chdir( ".." ); before
the require_once, which moves the current directory to SiteRootDir and
allows otherfuncs.php to be found ... is this the best way to solve this
problem?
Qualify relative paths by prepending $_SERVER['DOCUMENT_ROOT
2004 4:35 PM
> To: [EMAIL PROTECTED]
> Subject: [PHP] Website Architecture
>
>
> I've got a directory structure similar to this:
>
> SiteRootDir
>
>index.php
>
>dirA
> index.php
>
>dirB
> funcs.php
>
>otherfuncs.php
>
I've got a directory structure similar to this:
SiteRootDir
index.php
dirA
index.php
dirB
funcs.php
otherfuncs.php
In the SiteRootDir/index.php, I've got:
require_once( dirB/funcs.php );
in funcs.php, I've got:
require_once( otherfuncs.php );
which works because SiteRoot
17 matches
Mail list logo
