Query info as path

I found that there're more webpages have the query for a server-side script written as path info.

For example:
Instead of writing
http://mysite.com/perl/scriptname?param1=good&param2=bad

it's written as
http://mysite.com/perl/scriptname/param1=good/param2=bad

And internally let mod_rewrite or Apache::Request or something similar to do the parsing.

I wonder if there's an advantage for that?

I also see some sites use ";" to seperate the parameters too. One reason I think it that the "&" is bad for wml page or displaying at browser, right? (i have to write & to make it work for wml) But is that the only reason??

Thanks.

--
Bird

>> I wonder if there's an advantage for that?

Search Engine friendly, that is all. It's a waste of your server resources if you must do it. If you want to see rewrite rule examples, do a search under my username in this forum.

>> &" is bad for wml page

Not just wml page. It's commonly used character for all web scripting languages including mod_rewrite. Yes, you almost always need to escape it.