Re: URLing schemes and elegance

Justin Koivisto <spam@koivi.com> wrote in message news:<xXWBc.1945$m3.102320@news7.onvoy.net>...
> R. Rajesh Jeba Anbiah wrote:
>
> > Bit OT, but PHP oriented style issue...
> >
> > Just curious to know how many of you really use the URLs like
> > http://talks.php.net/index.php/Web+Services
> > And how many of you really liked or found it elegant? TIA
>
> Not I. I have been sticking with mod_rewrite for all my "se friendly"
> URIs. The best part about it is the hiding of technology. Afterall, if I
> have to switch a site over to jsp, asp or coldfusion, I can still keep
> the URIs without anyone (including the SEs) knowing that I am using a
> different tech.

Thanks for your comments. You seem to suggest mod_rewrite instead of
that scheme? But, if I'm right, they also seem to use mod_rewrite as
in the case:

http:talks.php.net/index.php/Web+Services
to
http:talks.php.net/index.php?page=Web+Services

Am I wrong?

--
| Just another PHP saint |
Email: rrjanbiah-at-Y!com

R. Rajesh Jeba Anbiah wrote:

> Justin Koivisto <spam@koivi.com> wrote in message
> news:<xXWBc.1945$m3.102320@news7.onvoy.net>...
>> R. Rajesh Jeba Anbiah wrote:
>>
>> > Bit OT, but PHP oriented style issue...
>> >
>> > Just curious to know how many of you really use the URLs like
>> > http://talks.php.net/index.php/Web+Services
>> > And how many of you really liked or found it elegant? TIA
>>
>> Not I. I have been sticking with mod_rewrite for all my "se friendly"
>> URIs. The best part about it is the hiding of technology. Afterall, if I
>> have to switch a site over to jsp, asp or coldfusion, I can still keep
>> the URIs without anyone (including the SEs) knowing that I am using a
>> different tech.
>
> Thanks for your comments. You seem to suggest mod_rewrite instead of
> that scheme? But, if I'm right, they also seem to use mod_rewrite as
> in the case:
>
> http:talks.php.net/index.php/Web+Services
> to
> http:talks.php.net/index.php?page=Web+Services
>
> Am I wrong?

Mod_rewrite usage doesn't even require the ".php" extension. All someone
browsing a site using mod_rewrite to rewrite the URLs would see is
www.site.com/content/whatever

The backend of the site could be php, perl, python, a CGI app, whatever, and the
URI's would stay the same even if someone switches the backend to an entirely
different programming language.