Hi,

On 8 November 2010 23:43, chung <chvng at mail.ntua.gr> wrote:

> Hi Nina, Tobias, All,
>
>  Do you suggest to drop the brackets just from the URL parameters (e.g.
> http://something.com/?params[]=... ) or in general for POSTed
> parameters.


Yes, all parameters.   URL encoded parameter names are rather inconvenient.


(have you tried Restlet  Reference.addQueryParameter() )?


> Let me remind that some services such as our filtering
> service and the consensus modeling algorithm (under construction)
> require arrays of data.


There is no problem to pass arrays by parameters which name doesn't include
any brackets. Parsing and interpreting the content of parameter content is
not restricted in any way by its name.


> I have sent already an email describing how can
> we handle arrays of parameters traveling over HTTP as well as their
> representation in RDF (and we have already started coding).
>

Whether parameter content is interpreted as array is a matter of
specification , not name.  I am not aware of anything in HTTP spec that
tells array parameters should have specific names (please correct me if I am
wrong), so no conflict with your efforts.

Regards,
Nina




>
> Best regards,
> Pantelis
>
> On Mon, 2010-11-08 at 18:23 +0200, Nina Jeliazkova wrote:
>
> > Hello All ,
> >
> > I would like to propose to drop square brackets from query parameter
> names
> > throughout OpenTox API , e.g. parameters like feature_uris[] to become
> > feature_uris.
> >
> > The reasons are
> >
> > 1) Some implementations (rightly) URL encode the parameter names in URL
> > query string, however, this is not correctly understood by all clients.
> >
> >
> http://localhost:8181/dataset/1?feature_uris%5B%5D=http%3A%2F%2Flocalhost%3A8181%2Ffeature%2F3
> >
> > 2) Not sure what was the original idea behind [] , but they don't really
> > impose any control on how many instances of particular parameter should
> be
> > there, so it's more of a syntax headache.
> >
> > 3) Finally, parameters like ?feature_uris%5B%5D=..  are not quite
> readable,
> > even if interpreted correctly.
> >
> > What do you think?
> >
> > Nina
> > _______________________________________________
> > Development mailing list
> > Development at opentox.org
> > http://www.opentox.org/mailman/listinfo/development
> >
>
>
> _______________________________________________
> Development mailing list
> Development at opentox.org
> http://www.opentox.org/mailman/listinfo/development
>