Re: [Hawkular-dev] Tenant Id - Not Part of URL
----- Original Message -----
From: "Thomas Segismont" <tsegismo(a)redhat.com>
To: hawkular-dev(a)lists.jboss.org
Sent: Tuesday, May 12, 2015 12:45:38 PM
Subject: Re: [Hawkular-dev] Tenant Id - Not Part of URL
Le 12/05/2015 15:17, Stefan Negrea a écrit :
>
> ----- Original Message -----
>> >From: "Thomas Segismont"<tsegismo(a)redhat.com>
>> >To:hawkular-dev@lists.jboss.org
>> >Sent: Tuesday, May 12, 2015 8:08:36 AM
>> >Subject: Re: [Hawkular-dev] Tenant Id - Not Part of URL
>> >
>> >You mean use_hawkularTenant_ instead of the_tenant_ query param? That
>> >makes less sense to me.
> I would use an identical query parameter so consumers that do not want/have
> the option to use headers can just append an identical query parameter.
> The hyphen is not reserved, therefore it can be used as part of the query
> parameter name or value without encoding. Correct me if I am wrong about
> the hyphen.
>
> http://tools.ietf.org/html/rfc3986#section-2.3
>
>
Please do not switch from top to bottom posting, or I might start to get
sick :p
Yes, "Hawkular-Tenant" is valid, but I'd prefer to pick something short
("tenant") for the query parameter fallback.
In fact, I'd prefer to have short names for all out-of-band query
parameters, like "pretty" to get a formatted JSON output.
We can alias any long name with short names (one or more). But we need to keep the long
names around to avoid confusion. Since this is a REST interface, I expect that the typical
consumer is another piece of software that does queries automatically. We should be
consistent in naming to make the API easier for the developer that codes against it. And
for the occasional manual use, we could throw in short aliases.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev