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: Wed, 31 Oct 2012 23:56:35 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-19582-2486-th8jsrSe65@http.www.w3.org/Bugs/Public/>

--- Comment #10 from Thomas Fossati <tho@koanlogic.com> ---
(In reply to comment #9)
> Surely all COAP hosts will thus be behind firewalls and inaccessible to
> world-wide accessible sites that would call registerProtocolHandler(), no?

I'm not sure to catch on to what you mean... but, yes: CoAP nodes (at least the
most constrained) won't be generally available in the wild.

We expect to find them behind these HTTP-CoAP proxies that act as application
layer gateways, bridging the www infrastructure on one side, and a constrained
intranet on the other).

A web application could registerProtocolHandler() to configure the needed
HTTP-CoAP gateway to use, and then link to coap://device/resource as if the
browser could speak natively with that constrained node.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 31 October 2012 23:56:37 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:35 UTC