Hi JC,
In the short term, the use case you mentioned will be restricted to privileged web apps/packaged apps/extensions/web pages in specific browser environments.
In the long term, as TVs and NAS evolve, this functionality will be brought back naturally to any web page.
As you suggested, the short term target is important as it should create enough NSD API use and JavaScript code base to enable the long term approach.
Regards,
Youenn
From: Jean-Claude Dufourd [mailto:jean-claude.dufourd@telecom-paristech.fr]
Sent: vendredi 4 octobre 2013 14:52
To: Giuseppe Pascale
Cc: public-device-apis@w3.org
Subject: Re: [discovery] Adding CORS to NSD API - proposal and issues
I remember the HNTF use cases: one was to have a web page discover a UPnP ContentDirectory and a UPnP MediaRenderer, and then propose to display some of the media from one on the other.
Oh sorry, this will not work with your existing 80" TV, nor with your NAS bought last year but already full of movies.
Is NSD of any use if it does not cover this use case ?
Best regards
JC
Le 4/10/13 14:38 , Giuseppe Pascale a écrit :
On Fri, Oct 4, 2013 at 2:32 PM, Jean-Claude Dufourd <jean-claude.dufourd@telecom-paristech.fr<mailto:jean-claude.dufourd@telecom-paristech.fr>> wrote:
JCD: I do not see how a standard that works with no devices is ever going to be useful.
It will work with those devices where manufacturers have explicitly decided they want to be exposed to the web.
/g
--
[Télécom ParisTech]<http://www.telecom-paristech.fr>
Jean-Claude DUFOURD<http://jcdufourd.wp.mines-telecom.fr>
Directeur d'études
Tél. : +33 1 45 81 77 33
37-39 rue Dareau
75014 Paris, France
[Site web]<http://www.telecom-paristech.fr>[Twitter]<https://twitter.com/TelecomPTech>[Facebook]<https://www.facebook.com/TelecomParisTech>[Google+]<https://plus.google.com/111525064771175271294>[Blog]<http://jcdufourd.wp.mines-telecom.fr>
