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: Tue, 21 Sep 2010 00:19:32 -0700
Message-ID: <AANLkTi=e=8oUBMWFayxSot7_MawcdhZPPMkZn6NbeZ9E@mail.gmail.com>
To: Adam Barth <w3c@adambarth.com>
Cc: Darin Fisher <darin@chromium.org>, Garrett Smith <dhtmlkitchen@gmail.com>, Julian Reschke <julian.reschke@gmx.de>, WebApps WG <public-webapps@w3.org>
+1 for 2 APIs - this whole multiple parameters with the same value is
too annoying imho and unnecessary for new web services . It should be
there only for old services that are also accessed via basic HTML
forms

cheers
devdatta

On 20 September 2010 23:56, Adam Barth <w3c@adambarth.com> wrote:
> Ok.  I'm sold on having an API for constructing query parameters.
> Thoughts on what it should look like?  Here's what jQuery does:
>
> http://api.jquery.com/jQuery.get/
>
> Essentially, you supply a JSON object containing the parameters.  They
> also have some magical syntax for specifying multiple instances of the
> same parameter name.  I like the easy of supplying a JSON object, but
> I'm not in love with the magical syntax.  An alternative is to use two
> APIs, like we current have for reading the parameter values.
>
> Adam
>
>
> On Mon, Sep 20, 2010 at 11:47 PM, Devdatta Akhawe <dev.akhawe@gmail.com> wrote:
>> 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 07:20:24 GMT

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