Re: [hono-dev] Custom path separator character

[Paolo Patierno <ppatierno@xxxxxxxx>]

+1 for me but let me just sharing with you some considerations ...

If we want to use something like Apache Kafka for storing telemetry data (or maybe events like we already do with ActiveMQ Artemis) then the "telemetry/DEFAULT_TENANT" isn't a valid name for a topic in Kafka (due to the "/" character).

In any case even if we'd like to use Apache Kafka, the Eclipse Hono APIs are designed for being accessible through the AMQP 1.0 protocol : in this case the AMQP - Kafka bridge protocol can be used for bridging the "telemetry/DEFAULT_TENANT" address (AMQP) to a Kafka topic replacing the "/" with "." (so the real name for the Kafka topic is "telemetry.DEFAULT_TENANT"). It means no problem for senders and receivers which connect to the Hono server and dispatch router (over AMQP 1.0) for sending/receiving telemetry but through Kafka internally. This configuration was tried in the past and it worked fine.

Just FYI ...

Thanks,

Paolo

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 Dejan Bosanac <dejanb@xxxxxxxxxxxx>
Sent: Wednesday, July 26, 2017 12:07 PM
To: hono developer discussions
Subject: Re: [hono-dev] Custom path separator character

 

+1 from me as well (as a guilty one for this). We don’t need it anymore

On Wed, Jul 26, 2017 at 2:07 PM, Frank Karsten (INST/ECS4) <Karsten.Frank2@xxxxxxxxxxxx> wrote:

Hi,

+1 from me - if we do not need it anymore, I find it rather confusing to have this kind of flexibility in the target and source addresses.



Mit freundlichen Grüßen / Best regards

Karsten Frank
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

-----Ursprüngliche Nachricht-----
Von: hono-dev-bounces@xxxxxxxxxxx [mailto:hono-dev-bounces@eclipse.org] Im Auftrag von Hudalla Kai (INST/ECS4)
Gesendet: Mittwoch, 26. Juli 2017 14:00
An: hono-dev <hono-dev@xxxxxxxxxxx>
Betreff: [hono-dev] Custom path separator character

Hi committers,

some of you may be aware of the fact that we support the definition of a custom path separator character for target and source addresses, e.g. using "." instead of "/" to form something like "telemetry.DEFAULT_TENANT" instead of "telemetry/DEFAULT_TENANT".

We introduced this only to support the usage of an earlier version of Artemis for brokering events, which at that time didn't support slashes in addresses. With the advent of Artemis 2.0 this limitation no longer exists so I wonder if we can (finally) remove the code for dealing with custom path separator characters from Hono.

WDYT?

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 _______________________________________________
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

--

Regards
--
Dejan Bosanac
http://sensatic.net/about