https://github.com/okleine/nCoAP

Java implementation of the CoAP protocol using netty
https://github.com/okleine/nCoAP

Last synced: about 1 month ago
JSON representation

Java implementation of the CoAP protocol using netty

• Host: GitHub
• URL: https://github.com/okleine/nCoAP
• Owner: okleine
• License: bsd-3-clause
• Created: 2012-01-27T13:04:52.000Z (over 12 years ago)
• Default Branch: master
• Last Pushed: 2018-03-20T19:19:31.000Z (over 6 years ago)
• Last Synced: 2024-02-10T23:33:26.339Z (5 months ago)
• Language: Java
• Homepage:
• Size: 7.25 MB
• Stars: 177
• Watchers: 19
• Forks: 57
• Open Issues: 9
• Metadata Files:
  • Readme: README.md
  • License: license.txt

Lists

• awesome-CoAP - nCoAP - This implementation of the Constrained Application Protocol bases on the asynchronous and event-driven network application framework Netty (thats where the 'n' in nCoAP comes from). (Libraries / Java)

README

        
## A JAVA implementation of the CoAP

This implementation of the Constrained Application Protocol bases on the asynchronous and event-driven network

application framework [Netty](http://netty.io) (thats where the 'n' in nCoAP comes from). The nCoAP framework

currently covers

* the raw protocol ([RFC 7252](https://tools.ietf.org/html/rfc7252)),

* the observation of CoAP resources ([RFC 7641](https://tools.ietf.org/html/rfc7641)),

* the blockwise transfer ([draft 19](https://tools.ietf.org/html/draft-ietf-core-block-19)),

* the identification of endpoints with changing IPs

([draft 01](https://tools.ietf.org/html/draft-kleine-core-coap-endpoint-id-01)) , and

* the CoRE Link Format ([RFC 6690](https://tools.ietf.org/html/rfc6690)).

but without DTLS (i.e. support for the coaps scheme). 

### Latest SNAPSHOT version (1.8.3-SNAPSHOT)

JavaDoc is available [here](https://media.itm.uni-luebeck.de/people/kleine/javadoc/ncoap-core/1.8.3-SNAPSHOT/). The

nCoAP project is organized in several maven modules, i.e.,

```xml

de.uzl.itm

ncoap-core

```

for the raw protocol implementation (including the extensions mentioned above). For CoAP application development this

is probably what you want. Note, that for several reasons some interfaces and package names changed since the latest

stable version (1.8.2). To use the latest bleeding edge version add the following to your pom.xml:

```xml

...

    

        itm-maven-repository-snapshots

        ITM Maven Snapshots Repository

        https://maven.itm.uni-luebeck.de/repositories/snapshots

    

...

```

...

```xml

...

    

        de.uzl.itm

        ncoap-core

        1.8.3-SNAPSHOT

    

...

```

### Examples for Client and Server 

The other models, i.e.,

```xml

de.uzl.itm

ncoap-simple-client

```

and

```xml

de.uzl.itm

ncoap-simple-server

```

provide simple CoAP applications for both, client and server. There intention is to highlight, how easy it is to

write such applications using ncoap.