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

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

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

--- Comment #12 from Thomas Fossati <tho@koanlogic.com> ---
(In reply to comment #11)
> I don't understand how that would work.
> [...]
> How is the Web Server going to implement the handler?

my scenario is:

a web application needs mashing up both CoAP and HTTP resources in one single
page.

On download/startup it asks the user to registerProtocolHandler() for a given
HTTP-CoAP proxy which is under its control.

If user agrees, native CoAP resources can then be interacted via HTTP back and
forth the translating gateway.

Another web application could do the same but with a different HTTP-CoAP proxy
in another tab at the same time. (It seems a pretty scalable approach to me.)

The security model is the one usually found in browsers: the user is requested
to opt in for a specific capability.

Also, since the browser speaks plain HTTP with the HTTP-CoAP proxy, there would
be no need to integrate the CoAP bits in to Mozilla, Chrome, Safari, IE, Opera,
or whatever.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 6 November 2012 19:06:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 6 November 2012 19:06:45 GMT