Dear Louis
This is a known problem, I did not have the time to fix so far. The documentation was unfortunately
lost, when the GitHub Issues section was removed by Eclipse.
Currently, the HTTP part is single-threaded. When the request takes long, e.g., because the forwarded
CoAP request is lost in the LoWPAN, all subsequent HTTP requests fail. The proxy was ported very quickly to the new implementation, but would need a proper re-design to fit the new staged architecture and concurrency model. HTTP should use a proper NIO approach…
Ciao
Matthias
Hi list,
We use the cf-proxy extensively from HTTP into our CoAP space. Unfortunately we ran into a problem. It appears as if the cf-proxy fails after a timeout
in a call to a resource. I.e. after the timeout, the exchange between HTTP and CoAP breaks down for new calls.
Has anyone else experienced this?
Regards
Dr. Louis Coetzee
CSIR Chief Engineer
Research Group Leader - Internet of Things
http://ioteg.meraka.csir.co.za
CSIR Meraka Institute, CSIR, South Africa
+27 12 841 3036
+27 83 407 4610
--
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard.
The full disclaimer details can be found at
http://www.csir.co.za/disclaimer.html.
This message has been scanned for viruses and dangerous content by
MailScanner,
and is believed to be clean.
Please consider the environment before printing this email.
