2012 IEEE 9th International Conference on Mobile Ad-Hoc and Sensor Systems (MASS 2012) 2012
DOI: 10.1109/mass.2012.6708525
|View full text |Cite
|
Sign up to set email alerts
|

Connecting the web with the web of things: lessons learned from implementing a CoAP-HTTP proxy

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2015
2015
2021
2021

Publication Types

Select...
6
4

Relationship

0
10

Authors

Journals

citations
Cited by 20 publications
(6 citation statements)
references
References 7 publications
0
6
0
Order By: Relevance
“…One of the big advantages of CoAP is in fact in its interoperability with HTTP, being that the both protocols are based on REST principles. For this interoperability to work it is necessary to deploy a proxy between them that will allow HTTP clients to request resources from CoAP servers and CoAP clients to request resources from HTTP servers [124] also presented in Fig. 11 (a).…”
Section: Multiple Protocol Solutions Based On a Combination Of Communmentioning
confidence: 99%
“…One of the big advantages of CoAP is in fact in its interoperability with HTTP, being that the both protocols are based on REST principles. For this interoperability to work it is necessary to deploy a proxy between them that will allow HTTP clients to request resources from CoAP servers and CoAP clients to request resources from HTTP servers [124] also presented in Fig. 11 (a).…”
Section: Multiple Protocol Solutions Based On a Combination Of Communmentioning
confidence: 99%
“…We also use the same protocol CoAP at the application level in our work but integrated it alongside the abstraction layer of graph-based querying and server layers. Translation like this between application layer protocols for IoT implementation has also been introduced in some other research works (e.g., [21][22][23]). These works mainly emphasise the mapping of IoT protocol CoAP and Internet communication of HTTP, using a service such as Firebase.…”
Section: Related Workmentioning
confidence: 99%
“…In this case, the proxy needs to include the implementation of both protocols, e.g., HTTP client with OCF server or CoAP client with HTTP server, etc. [ 26 , 27 ]. A specification of OCF presents an architecture of OCF device that includes the client, server, and translator to forwarding message between different network environments [ 28 ].…”
Section: Related Workmentioning
confidence: 99%