Hi,
ad 1) the link you are referring to points to the original project _proposal_ page. A lot has changed since then and you should not use if for reference. All relevant information can be found on the Hono website [1].
ad 2) Having a CoAP protocol adapter is something I would appreciate. Personally, I would indeed build it using Californium. Take a look at the existing protocol adapters in order to get started with it. They all are based on "org.eclipse.hono.service.AbstractProtocolAdapterBase"
which already provides the connection to the Device Registry and Hono Messaging component so that you can focus on implementing the device connectivity.
ad 3) yes, the Protocol Adapters always connect directly to the Hono Messaging component whereas the consumers connect to the AMQP 1.0 Messaging Network. See [2] for details
[1] https://www.eclipse.org/hono
[2]
https://www.eclipse.org/hono/architecture/component-view/Component-View/
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
From: hono-dev-bounces@xxxxxxxxxxx <hono-dev-bounces@xxxxxxxxxxx> on behalf of Thông Nguyễn Quốc <quocthong.ng@xxxxxxxxx>
Sent: Monday, June 26, 2017 14:39
To: hono developer discussions
Subject: Re: [hono-dev] Regarding the integration with other Eclipse project
Hi,
I have some questions regarding your last answer (sorry for asking a bit late on this matter), I hope you can clarify them for me:
ad 1) We definitely want to add more protocol adapters. In particular we would like to employ the code/artifacts from other Eclipse IoT projects for that purpose.
The most obvious thing to do is adding a CoAP protocol adapter based on Eclipse Californium. A LWM2M protocol adapter probably doesn't make much sense since the "management" of the devices already constitutes an application in the Hono sense, i.e. LWM2M would
probably better be implemented "northbound" of Hono. However, it would require the command & control direction, which is not (yet) available.
1) As you mentioned, LWM2M / Eclipse Leshan should be implemented in the northbound of Hono. However, in this drawing here on the Eclipse Hono project page [1], LWM2M is at the southbound of Hono. Therefore it makes me a quite confused about the position
of LWM2M / Leshan in "the big picture" of Hono,
2) I want to connect a device to Hono through CoAP, but at the current state of Hono, it doesn't have an official protocol adapter for CoAP. Is it technically possible to implement Californium into Hono sender blueprint [2] as a temporary implementation
of CoAP adapter ?
3) As I noticed, the Hono sender blueprint [2] does not implement the qdrouter as in Hono consumer [3], it connect directly to Hono instead (through Hono host and port). Are protocol adapters (HTTP, MQTT) the same with Hono sender and they connect directly
to Hono without AMQP network ?
Thank you in advance. I hope to receive your response soon.
Best regards,
T. Nguyen
|