- From: Dominique Hazael-Massieux <dom@w3.org>
- Date: Thu, 19 Sep 2013 14:01:47 +0200
- To: FABLET Youenn <Youenn.Fablet@crf.canon.fr>
- Cc: "public-device-apis@w3.org" <public-device-apis@w3.org>
Hi, Le jeudi 19 septembre 2013 à 09:00 +0000, FABLET Youenn a écrit : > In case the WG is not aware, implementation of the NSD API was > discussed on various browser engine mailing lists ([1], [2], [3]). > > Interesting feedback related to security issues was brought up. > [...] Thanks for the very good summary. > The discovery part of the NSD API specification seems already in a > pretty good shape. > The access granting part of the NSD API specification may take more > time to mature. > Given all of that, would it make sense to split the NSD API > specification in two documents? While I am in general sympathetic to the idea of reducing scope to broaden adoption and reduce development time, I'm sure what a pure discovery API would be useful for without the ability to communicate with the discovered services. Could you maybe detail a bit more what you have in mind here? Thanks, Dom > > [1] https://groups.google.com/a/chromium.org/forum/#! > topic/blink-dev/HT0KZKuTLxM > > [2] > http://www.mail-archive.com/webkit-dev@lists.webkit.org/msg23727.html > > [3] https://bugzilla.mozilla.org/show_bug.cgi?id=914579 > > [4] http://www.upnp-hacks.org/ > > > >
Received on Thursday, 19 September 2013 12:02:03 UTC