|  | <?xml version="1.0" encoding="utf-8" standalone="yes"?> | 
|  | <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> | 
|  | <channel> | 
|  | <title>Developer Guide on Eclipse Hono&trade;</title> | 
|  | <link>https://www.eclipse.org/hono/docs/dev-guide/</link> | 
|  | <description>Recent content in Developer Guide on Eclipse Hono&trade;</description> | 
|  | <generator>Hugo -- gohugo.io</generator> | 
|  | <language>en-us</language><atom:link href="https://www.eclipse.org/hono/docs/dev-guide/index.xml" rel="self" type="application/rss+xml" /> | 
|  | <item> | 
|  | <title>Building from Source</title> | 
|  | <link>https://www.eclipse.org/hono/docs/dev-guide/building_hono/</link> | 
|  | <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> | 
|  |  | 
|  | <guid>https://www.eclipse.org/hono/docs/dev-guide/building_hono/</guid> | 
|  | <description>Hono can be deployed using the pre-built Docker images available from our Docker Hub repositories. However, customizing and/or extending Hono&rsquo;s functionality requires building the images from source code. | 
|  | This page provides step by step instructions for getting the source code and building the Hono&rsquo;s Docker images from it. | 
|  | Prerequisites for building Hono Docker Creating Hono&rsquo;s container images using the Hono build process requires a Docker daemon running either locally or on another host you have access to.</description> | 
|  | </item> | 
|  |  | 
|  | <item> | 
|  | <title>AMQP Adapter Client for Java</title> | 
|  | <link>https://www.eclipse.org/hono/docs/dev-guide/amqp_adapter_client/</link> | 
|  | <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> | 
|  |  | 
|  | <guid>https://www.eclipse.org/hono/docs/dev-guide/amqp_adapter_client/</guid> | 
|  | <description>Eclipse Hono™ comes with a Java client for the AMQP adapter. It is intended for the implementation of (prototype) devices, (protocol) gateways or (end-to-end) tests. The client is based on Eclipse Vert.x. | 
|  | The starting point is the class AmqpAdapterClientFactory. | 
|  | The factory provides methods to get a receiver for receiving commands and a sender for each of the following actions: | 
|  | send a telemetry message send an event message send a response to a previously received command   Do not re-use sender instances The senders manage the underlying AMQP sender links, which are restored after temporary interruption of the connection (HonoConnection manages the automatic reconnection).</description> | 
|  | </item> | 
|  |  | 
|  | <item> | 
|  | <title>Consuming Messages from Java</title> | 
|  | <link>https://www.eclipse.org/hono/docs/dev-guide/java_client_consumer/</link> | 
|  | <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> | 
|  |  | 
|  | <guid>https://www.eclipse.org/hono/docs/dev-guide/java_client_consumer/</guid> | 
|  | <description>To illustrate how Eclipse Hono™ can be integrated with Java code, a simple application is provided that consumes telemetry and event data for devices belonging to the default tenant. | 
|  | It also includes support for Command and Control: | 
|  | if indicated by a received downstream message that contains a ttd value (refer to Device notifications for details) it tries to send a command to the device. If the value of ttd indicates that the device stays connected for an unlimited time (ttd == -1), the application will periodically repeat to send a command until notified the device is disconnected again (ttd == 0).</description> | 
|  | </item> | 
|  |  | 
|  | <item> | 
|  | <title>Implement a Custom Hono HTTP Protocol Adapter</title> | 
|  | <link>https://www.eclipse.org/hono/docs/dev-guide/custom_http_adapter/</link> | 
|  | <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> | 
|  |  | 
|  | <guid>https://www.eclipse.org/hono/docs/dev-guide/custom_http_adapter/</guid> | 
|  | <description><p>Eclipse Hono™ comes with a default <em>HTTP Adapter</em> which can be used to interact with devices via HTTP. | 
|  | The default HTTP Adapter also serves as a blueprint for implementing a <em>custom</em> HTTP protocol adapter.</p></description> | 
|  | </item> | 
|  |  | 
|  | </channel> | 
|  | </rss> |