[eluser]n0xie[/eluser]
[quote author="pbreit" date="1267488216"]Wow, amazing response. It is in fact a major problem for developers who hope to ever interface with other systems since querystrings are so widespread and have a very proper place in web development. [/quote]
It's funny you should mention that to someone who makes a living building interfaces to different webservices. FYI: outbound requests work fine without it.
Unless you provide an API, OR the interface you are talking redirects you back to your site with some parameters appended to the URL, it doesn't even matter if querystring is enabled or not. That's how non-interesting this issue is.
If you provide an API, you could just as well have used segmented url's. Or REST, XML-RPC, SOAP, JSON or any of the other zillion ways to transfer data over the wire without needing a querystring.
If you get redirected back (Paypall comes to mind), then YES you are forced to use querystrings. Oh noes, I have to set a boolean from false to true.
Again your argument would be valid if you had to jump through hoops to get querystrings to work like you would expect them. This is not the case: it's a damn configuration option.
Turn it on when you need to. If that's too hard for you, use a different framework.
