edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dale LaBossiere (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (EDGENT-375) Want a Watson IoTP device connector that uses HTTP
Date Wed, 08 Feb 2017 16:32:42 GMT

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

Dale LaBossiere reassigned EDGENT-375:

    Assignee: Dale LaBossiere

> 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

View raw message