| apps | ||
| common | ||
| doc | ||
| docker | ||
| futile/src/futile | ||
| ipes | ||
| openmtc-app/src/openmtc_app | ||
| openmtc-gevent | ||
| server | ||
| util | ||
| .gitignore | ||
| create-app-structure | ||
| create-binary-dist | ||
| create-binary-docker | ||
| LICENSE.md | ||
| MANIFEST.in | ||
| pylint.cfg | ||
| README.md | ||
| setup-gevent-all.py | ||
| setup-sdk.py | ||
| utils.py | ||
The OpenMTC SDK aims to provide developers with a convenient yet flexible tool to write oneM2M compliant applications. This includes network applications (NAs), gateway application (GAs), device applications (DAs), as well as interworking proxy entities (IPEs).
Table of Content
- Quick Start
- Introduction
- Deployment
- The MQTT Client
- Authentication Guide
- Installation of the OpenMTC SDK
- Overview REST API
- Write your first OpenMTC applications
- SDK - Using the Application Framework
- SDK - The low-level CSE Client
- SDK - The Data Model
- Examples
- Scripts
- Code Repository Structure
- Developer FAQ
Python
The OpenMTC SDK is written in and for the Python programming language. Users should therefore have at least a certain knowledge of Python and its paradigms. For this matter, the following material is recommended:
- The Python Homepage
- Expert Python Programming by Tarek Ziadé
- Code Like a Pythonista: Idiomatic Python by David Goodger
Feedback
Please create issues for any problems and direct any comments or feedback you are having to support@openmtc.org
Please let us know what you think. We are also very interested in any use case you are not able to implement with the SDK or if you find it difficult to do so.