- From: Alexander Adolf <alexander.adolf@me.com>
- Date: Sat, 30 Apr 2011 12:28:43 +0200
- To: Glenn Adams <glenn@skynav.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: <E1CEA36D-53C6-4AE5-95BE-045DC01C5BF8@me.com>
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
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Saturday, 30 April 2011 10:29:17 UTC