On 10 May 2010 13:58, Ashley Sheridan <ash@xxxxxxxxxxxxxxxxxxxx> wrote: > On Mon, 2010-05-10 at 13:15 +0200, Arno Kuhl wrote: > >> -----Original Message----- >> From: Alex Major [mailto:php@xxxxxxxxxxxx] >> 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. >> http://www.somesite.com/index.php?page=ViewUser >> http://www.somesite.com/index.php?page=ViewProduct >> 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 >> class. >> >> 2) Using SE friendly URL's like: >> http://www.somesite.com/products/22012/cool-game/ >> http://www.somesite.com/products/22013/other-game/ >> 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: >> http://www.somesite.com/viewproduct.php?product=.... >> http://www.somesite.com/viewuser.php?user=... >> This would appear to be the least developer friendly option? >> >> Alex. >> >> ============= >> >> 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". >> >> Cheers >> Arno >> >> >> > > > Personally, I go with option 3 (as Arno said, option 2 isn't really an > alternative option, it's something you can use with either 1 or 3) > > Consider a basic website with a small shopping cart and a blog. It would > seem crazy to have all the logic needed for the blog and the cart being > pulled in by PHP everytime you just needed to display a contact page. > Far easier to keep everything a bit more modular. That way, if you need > to update something, you update only a small part of the site rather > than some huge core file. > > But, if your needs are even more simple, say it's just a very small > brochure website you have, then running everything through a single > index.php might not be such a bad idea. > > Thanks, > Ash > http://www.ashleysheridan.co.uk > Option 1 with option 2 as a sidedish. Option 3 is a nightmare in my experience - a proper MVC approach is much better to work, maintain and assure the security of. Regards Peter -- <hype> WWW: http://plphp.dk / http://plind.dk LinkedIn: http://www.linkedin.com/in/plind Flickr: http://www.flickr.com/photos/fake51 BeWelcome: Fake51 Couchsurfing: Fake51 </hype> -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
