-----Original Message-----
From: Alex Major [mailto:p...@allydm.co.uk] 
Sent: 10 May 2010 12:39 PM

>From what I've seen and used, there seem to be three distinct ways of going
about it.

1)      Using a 'core' class which has a request handler in it. All pages in
the site are accessed through that one page, e.g.
This is one that I've personally used most after becoming familiar with a
bulletin board system several years ago. It means that pages are easily
created as all the template/session/database handling is done by the central

2)      Using SE friendly URL's like:
This approach seems to be becoming more common on the sites I frequent,
however by accounts I've read it seems to be more intensive on apache as it
requires a mod-rewrite function. 

3)      Using different PHP files for each page:
This would appear to be the least developer friendly option?


The second option doesn't really belong here, because you could go for
option 1 or option 3, and then decide whether to hide your implementation
behind a mod-rewrite. Option 2 would rather be part of a separate question
"what is the cost/benefit of using mod-rewrite".


PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to