We also need at least an encoding for slash, question mark and ampersand because they might be needed in future property
values. And the implementation should be easy with this well understood and broadly used encoding style.
Mit freundlichen Grüßen / Best regards
Marc Pellmann
Bosch Software Innovations GmbH
Core Products Development (INST/ECS4)
Schöneberger Ufer 89-91
10785 Berlin, Germany
www.bosch-si.de
Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB 148411 B
Executives: Dr.-Ing. Rainer Kallenbach, Michael Hahn
Von: hono-dev-bounces@xxxxxxxxxxx [mailto:hono-dev-bounces@xxxxxxxxxxx]
Im Auftrag von Paolo Patierno
Gesendet: Dienstag, 14. Februar 2017 09:37
An: hono developer discussions <hono-dev@xxxxxxxxxxx>
Betreff: Re: [hono-dev] Property bag at the end of topics for MQTT adapter?
The URI is a concept much more related to the web but we are trying to adapt this concept to an MQTT topic.
We know that at MQTT level using UTF-8 such encoding is not necessary but I agree on having that for consistency (in the previous mail I referred to use this "query string" even in the
HTTP REST adapter other than using only headers).
Paolo Patierno
Senior Software Engineer (IoT) @ Red Hat
Microsoft MVP on Windows Embedded & IoT
Hi everybody,
if the goal is to have a URI as a topic identifier, it should be URL encoded
to support more than "digits, letters, and a few graphic symbols" (like a slash
in "application/json") as per RFC3986:
"A URI is composed from a limited set of characters consisting of
digits, letters, and a few graphic symbols. A reserved subset of
those characters may be used to delimit syntax components within a
URI while the remaining characters, including both the unreserved set
and those reserved characters not acting as delimiters, define each
component's identifying data."
Best regards,
Sebastian
-----Ursprüngliche Nachricht-----
Von: hono-dev-bounces@xxxxxxxxxxx [mailto:hono-dev-bounces@xxxxxxxxxxx]
Im Auftrag von Hudalla Kai (INST/ESY1)
Gesendet: Dienstag, 14. Februar 2017 08:47
An: hono-dev@xxxxxxxxxxx
Betreff: Re: [hono-dev] Property bag at the end of topics for MQTT adapter?
On Tue, 2017-02-14 at 06:51 +0000, Pellmann Marc (INST/ECS4) wrote:
> Hi Kai,
>
> > We should probably declare a delimiter between the endpoint address
> > and the message properties. Similar to e.g. how it is done in URIs
> > ...
> > Since we are in control of the endpoint addresses we can make sure
> > that the delimiter is not a part of the address. In this case we
> > could define "?" as the delimiter. Is there also a delimiter for the
> > properties themselves?
> > In URIs the "&" character is used for that purpose. Does the "$"
> > have a particular meaning in your example?
>
> This is exactly what I had in mind (and also what Azure uses). The
> typical URI scheme with ? and &. You can see the ? in my example:
>
> telemetry/DEFAULT_TENANT/4711/?$content-
> type=application%2Fjson%3B%20charset%3Dutf-8
>
> At the moment I only use the content-type parameter. If we would have
> more parameters they would be separated by &. (The $ is the proposed
> prefix- character by Microsoft for system properties in separation to
> application properties).
>
It seems we are in agreement regarding the delimiters :-) Do we still think that we need to URL encode the properties then?
> Mit freundlichen Grüßen / Best regards Marc Pellmann
>
> Bosch Software Innovations GmbH
> Core Products Development (INST/ECS4)
> Schöneberger Ufer 89-91
> 10785 Berlin, Germany
> www.bosch-si.de
>
> Registered office: Berlin, Register court: Amtsgericht Charlottenburg,
> HRB
> 148411 B
> Executives: Dr.-Ing. Rainer Kallenbach, Michael Hahn
> _______________________________________________
> hono-dev mailing list
> hono-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/hono-dev
_______________________________________________
hono-dev mailing list
hono-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/hono-dev
_______________________________________________
hono-dev mailing list
hono-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/hono-dev
|
