Constrained Application Protocol: Difference between revisions

Revision as of 17:07, 1 September 2011

Revision as of 05:14, 7 September 2011

Line 8:

The CoRE group has proposed the following features for CoAP:

* RESTful protocol design minimizing the complexity of mapping with HTTP.
* Low header overhead and parsing complexity.
* URI and content-type support.
* Support for the discovery of resources provided by known CoAP services.
* Simple subscription for a resource, and resulting push notifications.
* Simple caching based on max-age.

The mapping of CoAP with [[HTTP]] is also definied, allowing proxies to be built providing access to CoAP resources via HTTP in a uniform way.

==Message Formats==