Re: A URL API

How about setParameter(name, value...) that takes var_args number of values?
Alternately, it could take either a DOMString or an Array<DOMString> for the
value. I prefer the var_args.

Also, getParameterByName and getAllParametersByName seem unnecessarily
wordy. How about getParameter/getParameterAll to match
querySelector/querySelectorAll? Putting "All" at the end is admittedly
awkward, but this is the uncommon case, so I'm OK with it for making the
common case less wordy.

Ojan

On Tue, Sep 21, 2010 at 4:56 PM, 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
> >>
> >
>
>