[UPHPU] Passing more than one $_GET variable
alvaro at epliant.com
Wed Aug 29 21:07:06 MDT 2007
Lonnie Olson wrote:
> On Wed, 2007-08-29 at 13:47 -0600, Rusty Keele wrote:
>> At Sheri's presentation last week she mentioned that Google
>> doesn't do very well with links that pass more than one variable. For
>> example: website.com?val1=98&val2=13 I have also found that when I try
>> to validate any XHTML code where I have links like this I always get an
>> error. Can somebody explain this to me? Is there some XHTML standard
>> that prohibits using more than one $_GET variable, or is it just good
>> coding practice to avoid multi-variable link references?
> In my opinion $_GET variables should only be used when the value is
> truly variable. Examples of it's use could be search queries.
> I am a big fan of what are called "clean URLs", or URLs without the ?=&
> gobbledygook. What looks better to you?
I'm not against pretty urls, I have done them before because *I* think
they're cool and they go well with the concepts of REST, but I would
argue that right about 0% of non-developer humans actually care what
urls look like. It's more of a cool thing for developers to do, than the
usability booster people make it out to be.
More information about the UPHPU