sitemap | name | title | layout | breadcrumbs | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
references.html |
Inventit Iot developer Network | References |
references |
|
- Version 1.1.0, The way to describe your models
- Version 1.1.2, HTTP based REST API set
- Version 1.0.0, Publish/Subscribe API specification
- Version 1.5.0, Server side javascript running on the sandbox server
- Version 1.1.1 (library version: 4.1.5), Android, OSGi and generic Java SE version of API set
- Version 1.0.0, C-based API set
There are several significant objects for MOAT IoT API sets. The respective elements are emerged on each MOAT IoT API set as illustrated below.
Key MOAT Objects | MOAT REST | MOAT js | MOAT Java/C |
---|---|---|---|
Web Clients | Server | Device/Gateway | |
Moat | (in a URL form) | ||
ModelMapper | N/A | (Stub) | |
Model | (incl. Stub) | ||
Device | N/A | ||
Dmjob | N/A |
- (in a URL form) means MOAT object appears on a URL path
- (Stub) means ModelMapper is always handled as a Stub object
- (incl. Stub) means that a model object can be created as a stub via API (
newModelStub()
). The model entity can be handled via another APIs (findByUid()
, etc.)