[
https://issues.apache.org/jira/browse/EDGENT-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale LaBossiere resolved EDGENT-377.
------------------------------------
Resolution: Fixed
resolved via https://github.com/apache/incubator-edgent/pull/280
Follow on tasks EDGENT-388 and EDGENT-389
> Support the IoT Gateway devices model
> -------------------------------------
>
> Key: EDGENT-377
> URL: https://issues.apache.org/jira/browse/EDGENT-377
> Project: Edgent
> Issue Type: Improvement
> Reporter: Dale LaBossiere
> Assignee: Dale LaBossiere
>
> Use case: I need to be able to write an Edgent application for my "IoT
> Gateway" device. An IoT Gateway device is a conduit for a collection of IoT
> devices that lack direct connection to the enterprise IoT hub. There can be
> IoT device events and commands that are targeted to the gateway device, as
> well as IoT device events and commands that are targeted to devices connected
> to it.
> The Edgent application needs to be able to deal with all of those types of
> IoT device events and commands.
> The Edgent gateway device application needs to be able to utilize the
> [IotProvider|https://github.com/apache/incubator-edgent/blob/master/providers/iot/src/main/java/org/apache/edgent/providers/iot/IotProvider.java]
> provider.
> I'll create a Pull Request with a starting point for API discussion.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
