- From: Mays, David <David_Mays@Comcast.com>
- Date: Wed, 8 Jun 2011 16:18:23 +0000
- To: Web and TV Interest Group WG <public-web-and-tv@w3.org>
> > >On 6/7/11 5:08 AM, "Dan Brickley" <danbri@danbri.org> wrote: > >>[snip] >>For a Web standard we can't really assume the devices are on >>the same LAN; I think this will be our biggest headaches. >> >>[snip] >>cheers, >> >>Dan > > > > I think that is an especially important point. In thinking about use cases in which service providers (E.g. Cable MSOs, broadcasters) would want to participate, it's easy to imagine a HN UA wanting to use non-HN communication to perform control functions on e.g. a cable set-top box. Then there are cases like mobile devices that may roam between HN WiFi and carrier 3G/4G networks. In this context, imo, applications should be able to continue to operate despite changes to network topography. In general, it hasn't been clear to me (as a newcomer to the TF) who/what is responsible for building/hosting the HTML/other user interfaces for the various UAs under discussion. For example, if I want to browse for services on my HN using a UA on my mobile phone, does the discovery protocol point my device's browser to a HN device that is hosting a particular HTML implementation of a service user interface? Please feel free to point me in a different direction if this is way off base. Dave
Received on Wednesday, 8 June 2011 17:19:24 UTC