[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [hono-dev] Name for high-priority endpoint
|
Also +1 for /event/*
-----Ursprüngliche Nachricht-----
Von: hono-dev-bounces@xxxxxxxxxxx [mailto:hono-dev-bounces@xxxxxxxxxxx] Im Auftrag von Hudalla Kai (INST/ESY1)
Gesendet: Mittwoch, 12. Oktober 2016 16:42
An: hono-dev@xxxxxxxxxxx
Betreff: Re: [hono-dev] Name for high-priority endpoint
+1 for /event/*
--
Mit freundlichen Grüßen / Best regards
Kai Hudalla
Chief Software Architect
Bosch Software Innovations GmbH
Schöneberger Ufer 89-91
10785 Berlin
GERMANY
www.bosch-si.com
Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB 148411 B;
Executives: Dr.-Ing. Rainer Kallenbach, Michael Hahn
On Di, 2016-10-11 at 13:17 +0000, Paolo Patierno wrote:
> Hi all,
>
> just to share what I and Dominik said on the #hono channel ...
>
> Dominik started with "alarm" (just as a working start name) but it's
> clear that, if we'll use this address even for life cycle events from
> devices, the "alarm" name is not so clear
>
> My suggestion is to use something like just "event" (i.e.
> /event/[tenant-
> id]/[device-id]) because an alarm is an event, a life cycle event is
> ... an event.
> The other option could be having different specific addresses for
> "alarm" and "lifecycle" but it means that in the future it could
> happen to add other addresses for other scenarios ... too much endpoints.
>
> Regards,
>
> 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 Guggemos Dominik (INST/ECS1) <Dominik.Guggemos@xxxxxxxxxxxx>
> Sent: Tuesday, October 11, 2016 1:07 PM
> To: hono developer discussions
> Subject: [hono-dev] Name for high-priority endpoint
>
> Hi all,
>
> we've been discussing about the name of the high-priority endpoint
> (see [1] and [2], the API will be similar to the Telemetry API) on the
> #hono chat, but couldn't find a good match so far.
>
> Hence the question to you: Where would you expect to send/receive
> high-priority messages to/from?
>
> So far we have defined the following endpoints:
>
> - telemetry/<tenant>/<device>
> - registration/<tenant>/<device>
> - control/<tenant>/<device>
>
> [1] https://github.com/eclipse/hono/issues/47
> [2] https://github.com/eclipse/hono/wiki/Security#resource-model
>
>
> Best regards
>
> Dominik Guggemos
>
> Bosch Software Innovations GmbH
> Engineering Cloud Services (INST/ECS1) Ziegelei 7
> 88090 Immenstaad
> GERMANY
> www.bosch-si.de
> www.blog.bosch-si.com
>
> Tel. +49 7545 202-396
> Fax +49 7545 202-301
> dominik.guggemos@xxxxxxxxxxxx
>
> 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
