W3C home > Mailing lists > Public > public-device-apis@w3.org > October 2013

Re: [discovery] Adding CORS to NSD API - proposal and issues

From: Giuseppe Pascale <giuseppep@opera.com>
Date: Fri, 4 Oct 2013 13:17:50 +0200
Message-ID: <CANiD0koV2tmW+HNB+SW6O-YcSjsmrPMFYtYwyEp9pWKzxMi6_A@mail.gmail.com>
To: Jean-Claude Dufourd <jean-claude.dufourd@telecom-paristech.fr>
Cc: Rich Tibbett <richt@opera.com>, Device APIs Working Group <public-device-apis@w3.org>
On Thu, Oct 3, 2013 at 3:11 PM, Jean-Claude Dufourd <
jean-claude.dufourd@telecom-paristech.fr> wrote:

>  JCD: If NSD requires modifications to SSDP, it will work with 0 devices
> at the beginning.
>

But if implementers refuse to implement NSD spec as is, we will never be
able to discover ANY type of device.
So regardless of people preferences, we need to be pragmatic.

As discussed in the other thread, we need to go for a default
implementation that is strict even though this means not supporting legacy
devices. We can imagine UA to hide behind a user setting the ability to
expose also legacy devices, but that would be a second step.

Of course use of NSD API in context where security is guaranteed in some
other way (app stores?) could be not restricted in the same way,



> This is a sure way to have a standard that will not be used.
>

I don't see how a standard that browser implementers refuse to implement is
ever going to be useful.
Received on Friday, 4 October 2013 11:18:38 UTC

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