W3C home > Mailing lists > Public > public-device-apis@w3.org > May 2014

RE: NSD spec implementation feedback

From: FABLET Youenn <Youenn.Fablet@crf.canon.fr>
Date: Mon, 19 May 2014 09:44:05 +0000
To: "w3c@fjhirsch.com" <w3c@fjhirsch.com>
CC: "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <ACC41E833067BD4FB8084DEBA2D866BE32DC7DE1@ADELE.crf.canon.fr>
> From: Frederick Hirsch [mailto:w3c@fjhirsch.com]
> Sent: jeudi 15 mai 2014 21:06
> To: FABLET Youenn
> Cc: Frederick Hirsch; public-device-apis@w3.org
> Subject: Re: NSD spec implementation feedback
> > But there are other means of communication (WebRTC, Raw socket API, chromecast, Presentation-API like communication channel...) that would all benefit from the NSD API.
> are you suggesting that we can further simplify by removing some communication specific aspects and abstracting more?

I am not sure that more abstraction is needed, though maybe to cope with discovery protocol data filtering.
Using the NSD API in the context of a browser extension may be much simpler than for an untrusted web app: no UI, no data filtering, no CORS, no whitelisting...
Reorganizing the spec so that browser developers can start implementing the easy bits in a consistent way may help adoption.

Received on Monday, 19 May 2014 09:44:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:33:07 UTC