<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<font face="Calibri">Top if you want to be cool :)</font><br>
<br>
I had never heard of this matrix parameter thing until your post.
But I sort of like how it extracts the global and orthogonal authz
info out of the path and query params. I'll throw my support in
this direction but reserve the right to change my mind. More
importantly, we need a consistent approach across Hawkular. If we
can't decide then I vote that Heiko choose and not let the
discussion linger very long so as to get the API published ASAP.<br>
<br>
<br>
<div class="moz-cite-prefix">On 5/13/2015 9:34 AM, Matt Wringe
wrote:<br>
</div>
<blockquote cite="mid:555352CA.9040900@redhat.com" type="cite">
<pre wrap="">On 12/05/15 01:45 PM, Thomas Segismont wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Le 12/05/2015 15:17, Stefan Negrea a écrit :
</pre>
<blockquote type="cite">
<pre wrap="">----- Original Message -----
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">From: "Thomas Segismont"<a class="moz-txt-link-rfc2396E" href="mailto:tsegismo@redhat.com"><tsegismo@redhat.com></a>
<a class="moz-txt-link-abbreviated" href="mailto:To:hawkular-dev@lists.jboss.org">To:hawkular-dev@lists.jboss.org</a>
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.
</pre>
</blockquote>
</blockquote>
<pre wrap="">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.
<a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/rfc3986#section-2.3">http://tools.ietf.org/html/rfc3986#section-2.3</a>
</pre>
</blockquote>
<pre wrap="">Please do not switch from top to bottom posting, or I might start to get
sick :p
</pre>
</blockquote>
<pre wrap="">
What is the correct convention for posting to the list? :) Top, bottom,
inline?
For the query parameter, is there any reason why we are using a query
parameter and not a matrix parameter?
Personally I think a matrix parameter makes a lot more sense
<a class="moz-txt-link-freetext" href="http://hawkular/metrics;tenant=foo/gauges/">http://hawkular/metrics;tenant=foo/gauges/</a>....
versus
<a class="moz-txt-link-freetext" href="http://hawkular/metrics/gauges/....?tenant=foo">http://hawkular/metrics/gauges/....?tenant=foo</a>
Always having to specify tenant at the end of the url seems strange to
be. Logically I would think that it should be applied to the metrics
resource itself and not to all the child resources.
Something like this would normally mean that the parameter 'a' is to be
applied to the 'foo/bar' resource:
<a class="moz-txt-link-freetext" href="http://foo/bar;a=b/baz">http://foo/bar;a=b/baz</a>
While, something like this would normally mean that the parameter 'a' is
to be applied to the 'foo/bar/baz' resource:
<a class="moz-txt-link-freetext" href="http://foo/bar/baz?a=b">http://foo/bar/baz?a=b</a>
</pre>
<blockquote type="cite">
<pre wrap="">
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.
_______________________________________________
</pre>
</blockquote>
<pre wrap="">_______________________________________________
hawkular-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/hawkular-dev">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>