| Re: Use of Includes [message #170946 is a reply to message #170907] |
Sat, 11 December 2010 12:42   |
sheldonlg
Messages: 166
Registered: September 2010
Karma:
|
Senior Member |
|
|
On 12/7/2010 9:55 AM, Bill Braun wrote:
> New to PHP.
>
> Have searched for answer without finding anything that seems to address
> it, save perhaps for situations where the script writes HTML markup
> before the header is called.
>
> When would it be preferable/required to chain scripts one to the next
> rather than use includes? (The question could be reversed, also.)
>
> Chaining:
>
> [php] // script1.php
> code;
> header("location: script2.php");
> [endphp]
>
> [php] // script2.php
> code;
> header("location: script3.php");
> [endphp]
>
> [php] // script3.php
> code;
> [endphp]
>
> Include:
>
> [php]
> // scriptname: script1.php
> code;
> include 'script2.php';
> include 'script3.php';
> [endphp]
>
>
> Bill B
I'm not sure I fully understand your question, but I'll try. First,
though, php is server side and provides html code that is presented to
the browser. So, whether you write all the code in one file, or use
includes/requires thus breaking it into two or more files, makes no
difference as far as the browser is concerned. It sees the same thing,
the whole page, either way.
I would chain scripts if there is a logical division of the actions.
For example, suppose it is a networking kind of thing and one page would
be user information for registration. This would then shift to another
page for upload of pictures after successful registration. Those are
two separate actions which are related to each other and putting them on
the same page would be cluttering. (This was a poor example because I
would just have a button with a link to a page to upload pictures after
registering and winding up on a landing page -- but it illustrates my
point).
I hope I understood your question correctly enough to be of some help.
--
Shelly
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]