- From: Rich Tibbett <richt@opera.com>
- Date: Tue, 20 Sep 2011 14:32:44 +0200
- To: Robin Berjon <robin@berjon.com>
- CC: public-device-apis@w3.org
There's also another angle to these proposals that is definitely worth mentioning. Both CORS and Discovery binding are proposed as complimentary solutions for enabling cross-origin messaging. In CORS the service provider authorizes other domains to access cross-origin resources. In a discovery proposal, the user authorizes this cross-origin messaging rather than the service provider. The end result is intended to be the same - authorized access to cross-origin resources - albeit with that authorization provided by a different actor in each proposal. It might be worth noting that point in the proposal itself. It's actually a proposal to solve a very real current problem with all the added benefits of also hooking in to already well-defined service discovery mechanisms. - Rich Robin Berjon wrote: > Hi all, > > there have been two primary proposals for a Discovery API that would enable web pages to (shockingly enough) discover services (on the device, the local network, or possibly remote) through common mechanisms such as DNS-SD or UPnP. > > One of them comes from Opera: > > http://people.opera.com/richt/release/specs/discovery/Overview.html > > And the other comes from Webinos: > > http://dev.webinos.org/deliverables/wp3/Deliverable32/static$42d2e5ab28271945244cdeb7579c65fd.html > > Ideally, we'd like to start with either of those and, if sensible, make sure it supports the use cases of the other. We're therefore calling for feedback from anyone interested in this topic. > > Please direct replies towards public-device-apis@w3.org where the work is taking place. Thanks! >
Received on Tuesday, 20 September 2011 12:33:25 UTC