Opened 13 years ago

Closed 13 years ago

#10 closed protocol enhancement (fixed)

HTTP Mapping

Reported by: zach@… Owned by: Don Sturek <dsturek@…>
Priority: major Milestone:
Component: coap Version:
Severity: - Keywords:
Cc:

Description

The HTTP mapping section needs to be written. There are probably three general topics here:

  1. Basic HTTP mapping

How basic GET/POST/PUT/DELETE requests are mapped. How to deal with the smaller subset of CoAP options and codes? How are options mapped?

  1. Proxying issues (with reference to Proxying section)

Are there any special issues here not covered in the Proxying section (when finished)? The basic issue is that an HTTP mapping entity will often also proxy.

  1. Sub/Not? mapping

To be done after the new Sub/Not? design is complete.

Change History (1)

comment:1 Changed 13 years ago by zach@…

  • Resolution set to fixed
  • Status changed from new to closed

Done in coap-01

Note: See TracTickets for help on using tickets.