W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2010

Re: A URL API

From: Devdatta Akhawe <dev.akhawe@gmail.com>
Date: Mon, 20 Sep 2010 23:47:38 -0700
Message-ID: <AANLkTi=hifMo5GoPXjBrvrdq70KSNwF_69_uuDM4+kdX@mail.gmail.com>
To: Darin Fisher <darin@chromium.org>
Cc: Garrett Smith <dhtmlkitchen@gmail.com>, Julian Reschke <julian.reschke@gmx.de>, Adam Barth <w3c@adambarth.com>, WebApps WG <public-webapps@w3.org>
or any webservice that likes to have lots of query parameters - Google
Search for example.

In general, why would you not want a robust way to make complicated
queries - those who are making simple queries and prefer simple one
liners can continue using it.


On 20 September 2010 23:42, Darin Fisher <darin@chromium.org> wrote:
> On Mon, Sep 20, 2010 at 11:02 AM, Garrett Smith <dhtmlkitchen@gmail.com>
> wrote:
>>
>> On 9/20/10, Julian Reschke <julian.reschke@gmx.de> wrote:
>> > On 20.09.2010 18:56, Garrett Smith wrote:
>> [...]
>> >> Requests that don't have lot of parameters are often simple one-liners:
>> >>
>> >> url = "/getShipping/?zip=" + zip + "&pid=" + pid;
>> >
>> > That's exactly the kind of code that will fail once "pid" and "zip"
>> > contain things you don't expecz.
>> >
>> >> What XHRs have complicated URL with a lot of query parameters?
>> >
>> > What XHRs?
>> >
>> IOW, what are the cases where an XHR instance wants to use a lot o query
>> params?
>>
>
> Probably when speaking to a HTTP server designed to take input from an HTML
> form.
> -Darin
>
Received on Tuesday, 21 September 2010 06:48:30 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:40 GMT