Mailing-List: contact dev-help@edgent.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@edgent.apache.org
Date: Tue, 21 Feb 2017 15:03:44 +0000 (UTC)
From: "Dale LaBossiere (JIRA)" <jira@apache.org>
To: dev@edgent.incubator.apache.org
Message-ID: <JIRA.13039267.1485889508000.19155.1487689424380@Atlassian.JIRA>
In-Reply-To: <JIRA.13039267.1485889508000@Atlassian.JIRA>
References: <JIRA.13039267.1485889508000@Atlassian.JIRA> <JIRA.13039267.1485889508108@jira-lw-us.apache.org>
Subject: [jira] [Resolved] (EDGENT-375) Want a Watson IoTP device connector
 that uses HTTP
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 21 Feb 2017 15:03:50 -0000


     [ https://issues.apache.org/jira/browse/EDGENT-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dale LaBossiere resolved EDGENT-375.
------------------------------------
    Resolution: Fixed

resolved via https://github.com/apache/incubator-edgent/pull/286

> Want a Watson IoTP device connector that uses HTTP
> --------------------------------------------------
>
>                 Key: EDGENT-375
>                 URL: https://issues.apache.org/jira/browse/EDGENT-375
>             Project: Edgent
>          Issue Type: Improvement
>          Components: Connectors
>            Reporter: Dale LaBossiere
>            Assignee: Dale LaBossiere
>
> Use case: I want to be able to write an Edgent device application that connects to the IBM Watson IoT Platform and publishes device events using its HTTP based protocol.  That would eliminate the need for my Edgent device to have an MQTT client installed.
> The current Watson IoT Platform connector, [IotpDevice|https://github.com/apache/incubator-edgent/blob/master/connectors/iotp/src/main/java/org/apache/edgent/connectors/iotp/IotpDevice.java] supports the MQTT based protocol.
> Adding support for an HTTP-based WIoTP connector would likely involve creating a class like "IotpHttpDevice implements IotDevice".  The IotDevice "events()" methods would use WIoTP HTTP publishing mechanism.  WIoTP does not support subscribing to device commands using HTTP so the IotDevice "commands()" method would be documented to throw UnsupportedOperationException.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)