|
|
Posted by McKirahan on 01/13/07 18:16
> "OmegaJunior" <omegajunior@spamremove.home.nl> wrote in message
news:op.tl04a0ne70mclq@cp139795-a.landg1.lb.home.nl...
> On Fri, 12 Jan 2007 06:36:51 +0100, McKirahan <News@McKirahan.com> wrote:
>
> > I am looking for feedback on an approach to using PHP.
> >
> > Below is a stripped down version of a Home page: "index.php".
> >
> > The content of the site is displayed in the middle of the page and
> > is "included" via "Page1.htm", "Page2.htm", or "Page3.htm".
> >
> > The page to be "included" is specified via the QueryString
> > which is specified in the navigational hyper links;
> > for example, "index.php?Page1".
> >
[snip]
> >
> > One advantage I see to this approach is that the "content" pages
> > are isolated from the "master" page and can be easily maintained.
> >
> > One disadvantage I see to this approach is that search engines
> > would not be able to catalog the site beyond the Home page.
> >
> > Are there other disadvantages (or other considerations) that I don't
see?
> >
> > Thanks in advance.
> >
> > P.S. I am new to PHP but have worked with ASP for years.
>
>
>
> 1) Good search engines *cough*Google*cough* will take the querystring
> into consideration while indexing.
> 2) For sake of ease, scalability, and security you may want to build a
querystring like ?id=1, instead of ?page1. Then you can read the page id
> with $_GET['id'].
> 3) Using this method of including, you should perform a check on file
> existence.
>
> Thanks for you reply.
I appreciate your ideas and may use them.
Why is "id=" easier and/or more scalable and/or more secure?
Navigation:
[Reply to this message]
|