W3C home > Mailing lists > Public > public-sysapps@w3.org > June 2013

Re: [runtime] Privileged Applications Extensions spec proposal

From: Janusz Majnert <j.majnert@samsung.com>
Date: Fri, 28 Jun 2013 08:57:39 +0200
Message-id: <51CD33E3.2060001@samsung.com>
To: public-sysapps@w3.org

On 2013-06-27 22:15, Kostiainen, Anssi wrote:
> On Jun 27, 2013, at 4:56 AM, Jonas Sicking <jonas@sicking.cc> wrote:
>
> Thanks for the feedback and use cases.
>
> [...]
>
>> downloadSize and downloadUpdate() is needed to build a update-UI. I.e. it's needed if a store wants to put an "update now" button in the store if it detects that the app the user is viewing is installed but out-of-date. Or if an app wants to put a "I'm out of date, click here to update me" banner at the top of itself when it detects that it's out-of-date. In both cases you might want to show the user the update size so that the user can make a decision if he/she wants to download the update.
> downloadSize and updateState are required to implement what you describe above -- which looks like a valid use case to me -- and should stay on the Application interface it seems.
I agree. The use case of any application becoming an app-store-app is 
valid and important.
>
> And with some changes to the normative language in downloadUpdate() we could make it an implementation detail whether user's consent is required to download an update, something like: "If the user agent has a reason to believe the operation could be costly (e.g. in terms of roaming costs for data transfer, or for other reasons), then the user agent MAY run the following substeps: [prompt the user etc.]".
>
> Does that sound reasonable?
>
> Another options would be to leave it up to the OS to inform the user of a potentially costly network being used (e.g. when switching the network, and/or after every X amount of bytes transferred) and not tie this to the operation itself.
IMHO it would be a good idea to make the spec as elastic as possible in 
this area. Various operators have various data-plans, there may also be 
regulatory differences in countries that should be catered for. What I'm 
trying to say is that the specification should allow for different 
prompting and data transfer control models to be implemented.

/Janusz
Received on Friday, 28 June 2013 06:58:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:36:13 UTC