W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2012

[Bug 19582] Add coap and coaps to the whitelist'ed scheme list

From: <bugzilla@jessica.w3.org>
Date: Tue, 30 Oct 2012 19:45:16 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-19582-2486-cWgIAqR5W3@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19582

--- Comment #8 from Thomas Fossati <tho@koanlogic.com> ---
(In reply to comment #7)
> Could you elaborate some more? How would this work? Where is the sensor, how
> is the remote server getting the data from the sensor, what does a coas: URL
> look like, why would anyone link to one, etc?

In the most basic scenario you have a sensor (say, reading the room's
temperature) hosted on a device not powerful enough to be a TCP/HTTP speaker --
let's realistically assume that it implements a minimal UDP/CoAP stack over a
802.15.4 radio.

The device publish its internal status via a resource, e.g. coap://device/temp
which, once dereferenced, returns some text/plain with the current measure in
Celsius degrees.  However, the browser can't directly access it because it
doesn't know CoAP.

So, the HTTP-CoAP gateway (say, http-coap.example.org:8080) may register itself
as the handler for requests having a  Request-URI with coap scheme, therefore
enabling access to the sensor by the browser: a "GET coap://device/temp
HTTP/1.1" would be sent to http-coap.example.org:8080, that handles the
syntactic translations needed to bridge the two.

A typical application may be a home appliance monitor which uses the HTTP-CoAP
gateway to access those resources that would be otherwise invisible to the
unconstrained hosts.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 30 October 2012 19:45:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 30 October 2012 19:45:21 GMT