2011
DOI: 10.17487/rfc6202
|View full text |Cite
|
Sign up to set email alerts
|

Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
31
0

Year Published

2011
2011
2020
2020

Publication Types

Select...
4
3
2

Relationship

0
9

Authors

Journals

citations
Cited by 44 publications
(31 citation statements)
references
References 2 publications
0
31
0
Order By: Relevance
“…Due to the wide range of existing formats to express graphical and theoretical models (e.g. VRML 15 , X3D 16 & MathML 17 ), we do not limit the specification and leave the model language choice up to the lab owner.…”
Section: J Models Service -Getmodelsmentioning
confidence: 99%
“…Due to the wide range of existing formats to express graphical and theoretical models (e.g. VRML 15 , X3D 16 & MathML 17 ), we do not limit the specification and leave the model language choice up to the lab owner.…”
Section: J Models Service -Getmodelsmentioning
confidence: 99%
“…In the case of HTTP/CoAP proxy, however, when the CoAP server finishes pushing notifications to the H/C proxy, the H/C proxy will have trouble delivering it to the registered client since it communicates with the client using HTTP but HTTP server does not have the ability to initiate a session. A remedy is to keep the HTTP client polling [10,11] the server whether there is a notification, but polling will incur much extra network traffic as Fig. 2 shows.…”
Section: A Coap Protocolmentioning
confidence: 99%
“…In the example, a dedicated connection is used for the CoAP observation relationship. In Step 1 the MCN issues, using HTTP long polling [29], a hanging HTTP GET request to the GW node. A hanging GET is used since the MCN wishes to observe the CoAP resource, that is, receive notifications when new data becomes available.…”
Section: Accessing Coap Resources From the Webmentioning
confidence: 99%