W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2010

RE: [WARP] Use cases for local network access

From: Marcin Hanclik <Marcin.Hanclik@access-company.com>
Date: Thu, 4 Feb 2010 16:40:06 +0100
To: Arve Bersvendsen <arveb@opera.com>, Stephen Jolly <stephen.jolly@rd.bbc.co.uk>, "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <FAA1D89C5BAF1142A74AF116630A9F2C28944DA23F@OBEEX01.obe.access-company.com>
Hi Arve,

>>Alternatively, should fine-grained distinction between the three, these
>>could alternatively be keywords in the existing origin attribute.
It matches the proposal at http://dev.w3.org/2006/waf/widgets-access-upnp/, although the name of that document is misleading.


Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452  |  Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanclik@access-company.com

-----Original Message-----
From: public-webapps-request@w3.org [mailto:public-webapps-request@w3.org] On Behalf Of Arve Bersvendsen
Sent: Thursday, February 04, 2010 4:16 PM
To: Stephen Jolly; public-webapps@w3.org
Subject: Re: [WARP] Use cases for local network access

On Tue, 02 Feb 2010 19:09:26 +0100, Stephen Jolly
<stephen.jolly@rd.bbc.co.uk> wrote:

> All,
> As actioned in the 21st Jan teleconference, here are the use cases that
> have motivated my specific proposal for supporting local network access
> in the WARP spec (see
> http://lists.w3.org/Archives/Public/public-webapps/2010JanMar/0173.html

> for details).
> 1. A developer wishes to write widgets that can connect to the web API
> exposed by a network-connected television or personal video recorder
> (aka digital video recorder) on their home network.  This API allows
> (for example) the channel being viewed to be changed or the list of
> scheduled recordings to be modified, via a user interface presented by
> the widget.

During this teleconference, I was asked to elaborate my position on this
topic.  The advantage of creating a definition of a local network is the
following variant of the use case:

A developer wants to write a widget that posts whatever channel the user
switches to on a network-connected TV to http://╬╝blogging.example.com/.

The problem, with WARP as is that, since the network address of said TV is
indeterminate, the developer's only option is to allow the widget to
connect to any URL it wishes (specifying '*' in origin, or add a large
(read: huge) set of origins in order to be able to do this.

My proposal would be to add a second attribute to the specification, a
boolean, such as origin-local, which would replace any IP address the user
agent considers to be local, link-local or even local-machine addresses.
Alternatively, should fine-grained distinction between the three, these
could alternatively be keywords in the existing origin attribute.

Arve Bersvendsen

Opera Software ASA, http://www.opera.com/


Access Systems Germany GmbH
Essener Strasse 5  |  D-46047 Oberhausen
HRB 13548 Amtsgericht Duisburg
Geschaeftsfuehrer: Michel Piquemal, Tomonori Watanabe, Yusuke Kanda


This e-mail and any attachments hereto may contain information that is privileged or confidential, and is intended for use only by the
individual or entity to which it is addressed. Any disclosure, copying or distribution of the information by anyone else is strictly prohibited.
If you have received this document in error, please notify us promptly by responding to this e-mail. Thank you.
Received on Thursday, 4 February 2010 16:06:26 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:22 UTC