forked from coap-technology/coap-technology.github.io
-
Notifications
You must be signed in to change notification settings - Fork 0
/
impls.html
263 lines (173 loc) · 14.7 KB
/
impls.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
---
layout: default
title: Implementations
---
<div class='jumbotron'>
<h2>Implementations</h2>
<p class='lead'>
CoAP is simple enough to implement from scratch for a simple application.
<br>
For applications where that is not desirable, generic implementations are becoming available for a variety of platforms.
Many of these implementations stay private, but some are published with liberal open-source licenses such as the Apache 2.0 or the MIT license.
</p>
</div>
<hr>
<div class='row-fluid'>
<div class='span4'>
<h2 id="constrained-devices">Constrained devices</h2>
<p>Implementations for <a href="http://tools.ietf.org/html/rfc7228">constrained devices</a> are typically written in C.</p>
<h3 id="erbium">Erbium</h3>
<p><img alt="" width="30%" style="float: right" src="http://people.inf.ethz.ch/mkovatsc/resources/erbium/Er_box_512.png" />
<a href="https://github.com/contiki-os/contiki">Contiki</a> is a widely used operating system for constrained nodes, being employed for research and product development.
Erbium is a full-fledged REST Engine and CoAP Implementation for Contiki.</p>
<p><a class="btn" href="http://people.inf.ethz.ch/mkovatsc/erbium.php">View details »</a></p>
<h3 id="libcoap">libcoap</h3>
<p>A C implementation of CoAP that can be used both on constrained
devices (running operating systems such as <a href="https://github.com/contiki-os/contiki">Contiki</a> or <a href="http://savannah.nongnu.org/projects/lwip/">LWIP</a>) and on a larger POSIX system.
Moreover, the library has been ported to <a href="http://tinyos.stanford.edu/tinyos-wiki/index.php/CoAP_-13">TinyOS</a> and <a href="https://github.com/RIOT-OS/RIOT/tree/master/pkg/libcoap">RIOT</a>.</p>
<p><a class="btn" href="http://libcoap.sourceforge.net/">View details »</a></p>
<h3 id="tinydtls">tinydtls</h3>
<p>To enable CoAP's security on a tiny device, a tiny implementation of DTLS
for
<a href="http://tools.ietf.org/html/rfc7228">Class 1</a>
devices:</p>
<p><a class="btn" href="http://tinydtls.sourceforge.net/">View details »</a></p>
<h3 id="smcp">SMCP</h3>
<p>A small-but-capable C-based CoAP stack suitable
for embedded environments. It supports observing, asynchronous
responses to requests, and more. Features that aren't used can
be removed to lower the footprint.</p>
<p><a class="btn" href="https://github.com/darconeous/smcp/">View details »</a></p>
<h3 id="microcoap">microcoap</h3>
<p>A C implementation that can be compiled for both Arduino and POSIX environments:</p>
<p><a class="btn" href="https://github.com/1248/microcoap">View details »</a></p>
<h3 id="cantcoap">cantcoap</h3>
<p>A C implementation that focuses on decoding and encoding,
leaving the actual protocol to the application.
“The user is expected to deal with retransmissions, timeouts, and message ID matching themselves. This isn’t as arduous as it sounds and makes a lot more sense on a constrained device.”</p>
<p><a class="btn" href="https://github.com/staropram/cantcoap">View details »</a></p>
<h3 id="lobaro-coap">Lobaro CoAP</h3>
<p>An MIT-licensed C implementation for constrained devices that
covers base CoAP, Observe, and Block, with demos for
<a href="http://www.lobaro.com/lobaro-coap-on-esp8266/">ESP8266</a> and
ZWIR4512 (Cortex M3).</p>
<p><a class="btn" href="http://www.lobaro.com/lobaro-coap/">View details »</a></p>
<h3 id="mr-coap">MR-CoAP</h3>
<p>MR CoAP (written in an embedded version of Java) is an implementation of CoAP, including the Observe and Block extensions, for <a href="http://www-03.ibm.com/press/us/en/pressrelease/42227.wss">IBM's</a> <a href="http://www.zurich.ibm.com/moterunner/">Mote Runner</a> operating system.</p>
<p><a class="btn" href="https://github.com/MR-CoAP/CoAP">View details »</a></p>
<h3 id="wakaama">wakaama</h3>
<p>The Wakaama project covers the <a href="http://technical.openmobilealliance.org/Technical/technical-information/release-program/current-releases/oma-lightweightm2m-v1-0">LWM2M</a> Protocol, CoAP, and DTLS
layers of the LWM2M protocol stack for all three logical
components: LWM2M Client, LWM2M Server and LWM2M Bootstrap
Server. An application using Wakaama can fill any LWM2M roles or
all of them at once. The CoAP and DTLS layers may be provided by external components.</p>
<p><a class="btn" href="http://eclipse.org/wakaama">View details »</a></p>
<h3 id="javascript-nodes">JavaScript nodes</h3>
<p>Some less constrained devices can run JavaScript right on the device.</p>
<p>The <a href="https://github.com/PeterEB/coap-shepherd">coap-shepherd</a> (server-side) and
<a href="https://github.com/PeterEB/coap-node">coap-node</a> (client-side) use CoAP, LWM2M, and the IPSO
Smart Object model as their base stone. This project is aiming
to provide a setup for full-stack IoT development with
JavaScript and Node.js.</p>
<p><a class="btn" href="https://github.com/PeterEB/coap-shepherd">View details »</a>
<a class="btn" href="https://github.com/PeterEB/coap-node">View details »</a></p>
</div>
<div class='span4'>
<p>CoAP is not only used between constrained devices, but also between them and more powerful systems such as cloud servers, home centrals, smartphones:</p>
<h2 id="server-side">Server-side</h2>
<h3 id="java">Java</h3>
<p><img alt="" width="30%" style="float: right" src="http://people.inf.ethz.ch/mkovatsc/resources/californium/Cf_box_512.png" />
One significant Java-based implementation of CoAP is <strong>Californium</strong>.</p>
<p><a class="btn" href="http://www.eclipse.org/californium/">View details »</a></p>
<p><strong>nCoAP</strong> is a Java implementation of the CoAP protocol using the
Netty NIO client server framework:</p>
<p><a class="btn" href="https://github.com/okleine/nCoAP">View details »</a></p>
<p><strong>Leshan</strong> is an <a href="http://openmobilealliance.org/">OMA</a> Lightweight M2M (<a href="http://technical.openmobilealliance.org/Technical/technical-information/release-program/current-releases/oma-lightweightm2m-v1-0">LWM2M</a>) server-side
implementation, on top of <a href="http://www.eclipse.org/californium/">Californium</a>.</p>
<p><a class="btn" href="https://github.com/eclipse/leshan">View details »</a></p>
<h3 id="c">C</h3>
<p>Several of the constrained-device implementations, such as
<a href="http://libcoap.sourceforge.net/">libcoap</a>, can also be used on the server side.</p>
<h3 id="c-1">C<em>#</em></h3>
<p><strong>CoAP.NET</strong> is an implementation in C# providing CoAP-based services to .NET applications.</p>
<p><a class="btn" href="https://github.com/smeshlink/CoAP.NET">View details »</a></p>
<p><strong>CoAPSharp</strong> is a lightweight library for building CoAP enabled
sensors and machines that also works with <a href="http://www.netmf.com">Microsoft .NET Micro
Framework</a>, with a
<a href="http://www.coapsharp.com/free-ebook-on-coap/">tutorial</a> for its
API:</p>
<p><a class="btn" href="http://www.coapsharp.com/">View details »</a></p>
<h3 id="erlang">Erlang</h3>
<p><strong>gen_coap</strong> is a pure Erlang implementation of a generic CoAP client and server:</p>
<p><a class="btn" href="https://github.com/gotthardp/gen_coap">View details »</a></p>
<h3 id="go">Go</h3>
<p><a class="btn" href="https://github.com/dustin/go-coap">View details »</a></p>
<h3 id="javascript-nodejs">JavaScript (node.js)</h3>
<p><strong>node-coap</strong> is a client and server library for
CoAP modelled after the <em>http</em> module. Install with <code>npm install
coap</code>.</p>
<p><a class="btn" href="https://github.com/mcollina/node-coap">View details »</a></p>
<p><strong>CoAP-CLI</strong> is a command line interface for CoAP, built on node.js and node-coap.
Install with <code>npm install coap-cli -g</code>.</p>
<p><a class="btn" href="https://github.com/mcollina/coap-cli">View details »</a></p>
<h3 id="python">Python</h3>
<p><strong>txThings</strong> is a CoAP library based on Python's <a href="http://twistedmatrix.com/">Twisted</a> framework:</p>
<p><a class="btn" href="https://github.com/siskin/txThings/">View details »</a></p>
<p><strong>aiocoap</strong> implements CoAP natively on Python 3.4's <a href="https://docs.python.org/3.4/library/asyncio.html">asyncio</a>
mechanisms, and provides command line tools for resource
fetching and proxying:</p>
<p><a class="btn" href="https://github.com/chrysn/aiocoap">View details »</a></p>
<p><strong>CoAPthon</strong> is a python library for the CoAP protocol, with a
branch available that uses the Twisted framework.</p>
<p><a class="btn" href="https://github.com/Tanganelli/CoAPthon">View details »</a></p>
<h3 id="ruby">Ruby</h3>
<p>Install a client library with: <code>gem install coap</code></p>
<p><a class="btn" href="https://github.com/nning/coap">View details »</a></p>
<p>Based on this, a Rack-based server implementation provides
compatibility with Rails, Sinatra, and other popular Web
frameworks: <code>gem install david</code></p>
<p><a class="btn" href="https://github.com/nning/david">View details »</a></p>
<h3 id="rust">Rust</h3>
<p><a class="btn" href="https://github.com/Covertness/coap-rs">View details »</a></p>
</div>
<div class='span4'>
<h2 id="browser-based">Browser-based</h2>
<p><img alt="" width="30%" style="float: right" src="http://people.inf.ethz.ch/mkovatsc/resources/copper/Cu_box_512.png" />
<strong>Copper</strong> is an extension for Firefox to enable direct access to CoAP resources from a browser.
<a class="btn" href="http://people.inf.ethz.ch/mkovatsc/copper.php">View details »</a></p>
<h2 id="smartphones">Smartphones</h2>
<p>Some implementations are specifically targeting mobile devices such as smartphones and tablets. These tend to differ between platforms:</p>
<h3 id="ios-osx">iOS, OSX</h3>
<p>A simple iOS client implementation has been written by Wojtek Kordylewski in Objective-C.</p>
<p><a class="btn" href="https://github.com/stuffrabbit/iCoAP">View details »</a></p>
<p>CoAP client and server libraries are also available in Swift:</p>
<p><a class="btn" href="https://github.com/stuffrabbit/SwiftCoAP">View details »</a></p>
<h3 id="android">Android</h3>
<p>Many Java components work out of the box on Android. For
instance, <a href="http://www.eclipse.org/californium/">Californium</a> and <a href="https://github.com/okleine/nCoAP">nCoAP</a> can be used on an
Android device.</p>
<p><a class="btn" href="http://www.eclipse.org/californium/">View details »</a>
<a class="btn" href="https://github.com/okleine/spitfirefox">View details »</a></p>
<p><strong>Aneska</strong> is a simple CoAP browser based on <a href="https://github.com/siskin/txThings/">txThings</a>, installable from Google Play.</p>
<p><a class="btn" href="https://play.google.com/store/apps/details?id=pl.sixpinetrees.aneska">View details »</a></p>
<h2 id="commercial-implementations">Commercial implementations</h2>
<p>We are just beginning to collect information on closed-source commercial implementations.
If yours is missing, please
<a href="https://github.com/coap-technology/coap-technology.github.io/issues/new">create a github issue</a>
(free github account required) or
<a href="mailto:cabo@tzi.org?subject=coap.technology">just send mail</a> to us!</p>
<h3 id="arm-mbed">ARM mbed</h3>
<p>A CoAP-based implementation is available with the <a href="https://www.mbed.com/en/">mbed OS</a>.
The “mbed client” implementation (which contains a CoAP server) implements the OMA LWM2M protocol:</p>
<p><a class="btn" href="https://docs.mbed.com/docs/mbed-client-guide/en/latest/">View details »</a></p>
<h3 id="onempower-interdigital">oneMPOWER (InterDigital)</h3>
<p>The InterDigital <a href="http://www.interdigital.com/page/coap">oneMPOWER</a> platform is a cloud based solution
for IoT service providers. It implements the complete oneM2M
Service Layer running on the CoAP and HTTP web transfer
protocols.</p>
<p><a class="btn" href="http://www.interdigital.com/page/coap">View details »</a></p>
<h3 id="thethingsio">thethings.io</h3>
<p>thethings.iO is an IoT platform that stores data from Things and
offers tools to analyze it.</p>
<p><a class="btn" href="https://developers.thethings.io/makers-coap.html">View details »</a></p>
</div>
</div>