Re: webtv-ISSUE-24 (igarashi): Local Link of web applications [HOME_NETWORK_TF]

On Thu, 23 Jun 2011 09:20:30 +0200, Igarashi, Tatsuya  
<Tatsuya.Igarashi@jp.sony.com> wrote:

> Hi,
>
>> -----Original Message-----
>> From: Mark Watson [mailto:watsonm@netflix.com]>
>> On Jun 21, 2011, at 3:22 PM, Giuseppe Pascale wrote:
>>
>> > On Tue, 21 Jun 2011 12:40:45 +0200, Mark Watson <watsonm@netflix.com>
>> > wrote:
>> >
>> > can confirm).
>> > In general we seems to have 2 general use cases:
>> >
>> > - communicate with services using existing and established protocols
>> > (UPnP, Bonjour, etc)
>>
>> These are protocols for establishing connectivity, rather than  
>> application
>> protocols
>
> I guess that Giuseppe's intent is that services are UPnP or Bonjour  
> specific services. Since UPnP SSDP and Bonjour are the network protocols  
> for Discovery,
> the first general use case can be clarified as follows;
>
> - enable communication with services using existing and established  
> application protocols (UPnP services, Bonjour services, etc).
>
Yes, thanks for clarifying and forgive my "improper" use of terminology.


>>
>> > - enable communication between 2 applications with a "proprietary"
>> protocol
>
> I believe that the webtv-ISSUE-24 corresponds to the 2nd general use  
> case.
>
>>
>> Aren't the things in the first bullet the means that are used to achieve
>> the aim of the second bullet ? Not sure how I understand these as 2  
>> use-cases ?
>
> I think that the two general use cases are independent. But the common  
> underlying network protocols, e.g. UPnP SSDP or Bonjour discovery, may  
> be used to realize the both use cases.
>
Exactly. What I was trying to underline is the following difference:
in the first case (after discovery) you have an application sending  
messages to a device that runs a UPnP/Bonjour service.
in the second case (after discovery) we only want to exchange messages  
between two web applications.

so the first case may impose some additional requirements on the API we  
aim to design, enforced by the UPnP/Bonjour services,
in the second case the (already existing) web messaging API [1] should be  
enough.

But of course, as you say, discovery is needed in both cases and in some  
usecases it could be implemented using UPnP/Bonjour also for the second  
case.

P.S.
forgive my my "improper" use of UPnP/Bonjour,
I think the right interpretation of these terms should be clear from the  
context.


[1] http://dev.w3.org/html5/postmsg/
/g




> Thank you.
>
> -***---***---***---***---***---***---***---***---***--***---***---***-
> Tatsuya Igarashi (Tatsuya.Igarashi@jp.sony.com)
> NS Development Dept. Technology Development Group
> Sony Corporation
> (Voice) +81-3-5435-3252 (Fax) +81-3-5435-3274
>
>


-- 
Giuseppe Pascale
TV & Connected Devices
Opera Software - Sweden

Received on Monday, 1 August 2011 09:32:51 UTC