coap与http比较

his page compares CoAP vs HTTP and describes difference between CoAP and HTTP protocols. CoAP stands for Constrained Application Protocol and HTTP stands for Hyper Text Transfer Protocol. It provides link to difference between HTTP and HTTPS.

CoAP-Constrained Application Protocol

This protocol is upgraded version of HTTP. It is designed for resource constained applications such as IoT/WSN/M2M etc. It is based on UDP. It uses ACK messages so that it will become reliable like TCP. It has low latency and consumes lesser power compare to HTTP. 
Refer CoAP Protocol basics➤.

HTTP-Hyper Text Transfer Protocol

Figure-1 depicts HTTP protocol used between client and server as unsecured connection. HTTPS version of HTTP is used to provide secured connection. HTTP is used mainly to view web pages or websites. The protocol is designed for internet based applications and devices where power and any other constaints are not there.It is TCP based protocol. 
Refer HTTP and HTTPS basics➤.

Following is the tabular difference between CoAP and HTTP protocols.

Feature	CoAP	HTTP
Protocol	It uses UDP.	It uses TCP.
Network layer	It uses IPv6 along with 6LoWPAN.	It uses IP layer.
Multicast support	It supports.	It does not support.
Architecture model	CoAP uses both client-Server & Publish-Subscribe models.	HTTP uses client and server architecture.
Synchronous communication	CoAP does not need this.	HTTP needs this.
Overhead	Less overhead and it is simple.	More overhead compare to CoAP and it is complex.
Application	Designed for resource constrained networking devices such as WSN/IoT/M2M.	Designed for internet devices where there is no issue of any resources.