Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [hono-dev] Property bag at the end of topics for MQTT adapter?

I know that the URL encoding could be not needed ... I know that using the HTTP REST adapter you can pass such information using the HTTP headers but what if we could offer a consistent experience to the user that could use the same query string in the HTTP REST adapter as well .... so in this case the URL encoding becomes mandatory (having the same for the MQTT adapter ... I know ... even if here the URL encoding isn't needed :-))


Paolo Patierno
Senior Software Engineer (IoT) @ Red Hat
Microsoft MVP on Windows Embedded & IoT
Microsoft Azure Advisor 

Twitter : @ppatierno
Linkedin : paolopatierno
Blog : DevExperience



From: hono-dev-bounces@xxxxxxxxxxx <hono-dev-bounces@xxxxxxxxxxx> on behalf of Hudalla Kai (INST/ESY1) <Kai.Hudalla@xxxxxxxxxxxx>
Sent: Tuesday, February 14, 2017 7:47 AM
To: hono-dev@xxxxxxxxxxx
Subject: 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

Back to the top