Re: [hono-dev] Redundant(?) properties in API messages

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [hono-dev] Redundant(?) properties in API messages

From: Gordon Sim <gsim@xxxxxxxxxx>
Date: Wed, 27 Apr 2016 15:26:56 +0100
Delivered-to: hono-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/hono-dev>
List-help: <mailto:hono-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/hono-dev>, <mailto:hono-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/hono-dev>, <mailto:hono-dev-request@eclipse.org?subject=unsubscribe>
Organization: Red Hat UK Ltd, Registered in England and Wales under Company Registration No. 3798903, Directors: Michael Cunningham, Michael O'Neill, Eric Shander
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1

On 27/04/16 14:14, Hudalla Kai (INST/ESY1) wrote:

We will now try to use a sender (with target address) per tenant when forwarding the telemetry messages to the dispatch router.

However, since I think that being able to authorize at the device level (when receiving telemetry data) as well, it would be great if the dispatch router would at some time support what you promised :-)

Any chance for that?


Yes, I think there will be more flexible routing at some point.

Follow-Ups:
- Re: [hono-dev] Redundant(?) properties in API messages
  - From: Paolo Patierno

References:
- [hono-dev] Redundant(?) properties in API messages
  - From: Guggemos Dominik (INST/ECS1)
- Re: [hono-dev] Redundant(?) properties in API messages
  - From: Gordon Sim
- Re: [hono-dev] Redundant(?) properties in API messages
  - From: Hudalla Kai (INST/ESY1)
- Re: [hono-dev] Redundant(?) properties in API messages
  - From: Gordon Sim
- Re: [hono-dev] Redundant(?) properties in API messages
  - From: Guggemos Dominik (INST/ECS1)
- Re: [hono-dev] Redundant(?) properties in API messages
  - From: Paolo Patierno
- Re: [hono-dev] Redundant(?) properties in API messages
  - From: Gordon Sim
- Re: [hono-dev] Redundant(?) properties in API messages
  - From: Hudalla Kai (INST/ESY1)

Prev by Date: Re: [hono-dev] Redundant(?) properties in API messages
Next by Date: Re: [hono-dev] Telemetry API & Dispatch Router Docker images
Previous by thread: Re: [hono-dev] Redundant(?) properties in API messages
Next by thread: Re: [hono-dev] Redundant(?) properties in API messages
Index(es):
- Date
- Thread

Breadcrumbs