Mailing-List: contact dev-help@edgent.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@edgent.apache.org
From: Dale LaBossiere <dml.apache@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\))
Subject: synergy with Apache Mynewt
Message-Id: <5F6A98B2-CFDA-418F-A048-61CC9E7FCAD8@gmail.com>
Date: Wed, 17 May 2017 14:41:29 -0400
Cc: aditi@apache.org
To: dev@edgent.apache.org
archived-at: Wed, 17 May 2017 18:41:38 -0000

Hey all,

Will and I had a chat with a couple of Apache Mynewt folks.

At a very high level, Mynewt is a cool RTOS for micro controllers.
Mynewt also has some nice dev tools for building and deploying images.

Mynewt devices seem most typically to be too constrained for running =
java-Edgent.
I didn=E2=80=99t ask but presumably even if we had a C++ based =
API/runtime
the cost/benefit to us seems like it wouldn=E2=80=99t be justified =
because...

A common configuration would be for a collection of Mynewt devices
to connect to the cloud via an IoT gateway.  They are promoting? =
(developing?)
a RPi based gateway.  A portion of Mynewt runs as a process, acting as
the conduit to the actual Mynewt devices.

They have APIs available for ingesting sensor data from these devices,
so it=E2=80=99s merely a matter of creating a connector that uses them =
in order
to make it easy to write IoT Gateway based Edgent apps that=20
ingest the data and do their thing.

I=E2=80=99ll look into this more when I=E2=80=99m back in the office.

If you have any interest or info to add, please chime in!

=E2=80=94 Dale