- From: <bugzilla@jessica.w3.org>
- Date: Tue, 06 Nov 2012 19:34:28 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19582 --- Comment #14 from Thomas Fossati <tho@koanlogic.com> --- (In reply to comment #13) > If the proxy is under the site's control (on the public Internet), how can > it access the "native CoAP resources" on the user's network (behind the > user's firewall)? Ah, now I understand what your concern is ! Scenario 1: "home" CoAP sensors and actuators are typically domestic appliances, light bulbs, meters, etc. Both the browser and the proxy are behind the home gateway, thus no ACL/NAT/firewall prevents browser from interacting with the the HTTP-CoAP proxy. Scenario 2: "city" CoAP sensors and actuators are smog/temperature/etc. detectors scattered in the city territory. HTTP-CoAP proxy is in the public internet and can be freely contacted by any browser. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 6 November 2012 19:34:29 UTC