- From: Glenn Adams <glenn@skynav.com>
- Date: Sat, 30 Apr 2011 18:34:39 +0700
- To: Alexander Adolf <alexander.adolf@me.com>
- Cc: Dave Raggett <dsr@w3.org>, Mark Watson <watsonm@netflix.com>, "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>
- Message-ID: <BANLkTim6se9usBnGJ4fXvLjcGeJ04_UBfA@mail.gmail.com>
There is no DLNA "device discovery Java API". At present, DLNA has no HN API other than that defined by UPnP. DLNA guidelines reference CEA-2014-A, but do not yet reference CEA-2014-B, which does define a JS HN API which I previously forwarded to this list. Those JS HN APIs are not present in CEA-2014-A, but were introduced in 2014-B. G. On Sat, Apr 30, 2011 at 5:28 PM, Alexander Adolf <alexander.adolf@me.com>wrote: > Dear Glenn, > Dear Colleagues, > > On 2011-04-17, at 02:58 , Glenn Adams wrote: > > > Yes, that would work well enough for interbrowser HN interaction, but my > > primary concern is supporting (at least) UPnP 1.1 in a manner that > provides > > as full as possible access to all protocol elements, both for > > unicast/multicast notifications/events and unicast request/response > > interactions. > > [...] > > > +1 from my side. As I mentioned some time ago, DVB has adopted DLNA's > device discovery which is based on UPnP. So there might be a point sending > out a liaison to DLNA asking them for information on their device discovery > Java API. > > But there are also quite some Open Source implementations that are > compatible with DLNA: http://elinux.org/DLNA_Open_Source_Projects > > Assuming we had that in place, one could very easily implement and use the > MHP 1.3 Java APIs for service discovery. The most prominent might be these > two: > > getServiceProviderRecords > Element[] getServiceProviderRecords() > Provides access to the SD&S Service Provider records > Returns: > an array of SD&S Service Provider Records > > getServiceOfferingRecords > Element[] getServiceOfferingRecords(java.lang.String domainName) > Provides access to the SD&S Service Offering records > for a particular Service Provider > Parameters: > domainName - Domain name of the service provider for > which offerings are requested > Returns: > an array of SD&S Service Offering Records, including > BCG records > > Get all service providers, the see what they offer. > > Full JavaDoc is here: http://www.mhp.org/specs/GEM_1_3_JavaDocs.zip > > > Thanks and cheers, > > --alex
Received on Saturday, 30 April 2011 11:35:29 UTC