W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2008

[Widgets] R21. Resource Declarations. Was RE: Request for Comments on Widgets 1.0 Requirements Last Call WD

From: Marcos Caceres <marcosscaceres@gmail.com>
Date: Fri, 8 Aug 2008 15:04:49 +1000
Message-ID: <b21a10670808072204s52125d77id93e10e0135b5658@mail.gmail.com>
To: BS3131@att.com, public-webapps <public-webapps@w3.org>

Hi Bryan,
I'm wondering if you could help me understand "R21. Resource
Declarations", which was proposed in your feedback [1]:

> R21. Resource Declarations
>
> A conforming specification must specify a means for declaring that the
> instantiated widget will have an impact on sensitive device or network
> resources, which may impact device performance or the user experience.
>
> Motivation:
>
> Security, current development practice or industry best-practices.
>
> Rationale:
>
> To declare the resource requirements of the widget, allowing the
> widget user agent to respond accordingly by adjusting its resource
> policies and warning the end-user. Example of resource sensitive
> services that could require notification are automated operation
> involving network access or screen display, which can impact overall
> service cost and device battery life; or persistent storage
> requirements, which can affect device performance and reliability of
> the environment for other applications.
>

I'm not sure I understand, from a developer's perspective, how I would
declare resource use particularly because it seems so relative and
subjective. For example, if I had created a widget and tested it on my
super-phone I might think that it is not very resource demanding (this
might be because the widget implementation running on my phone is very
efficient and light weight). However, another widgets implementation
might not be as efficient and hence it may use a lot of resources (but
this is not the fault of the widget, it is the fault of the
implementaiton). Another problem is that one phone might have limited
resources by design (eg. limited RAM and storage) or because other
applications are hogging resources.

Maybe the requirement should be that the user agent should report to
the user when a widget is hogging resources; however this seems more
like something that would be best left to implementers.

Can you maybe show us a usage scenario for what you have in mind for
this requirement. How do you envision this would work?

Kind regards,
Marcos

[1] http://lists.w3.org/Archives/Public/public-webapps/2008JulSep/0298.html

-- 
Marcos Caceres
http://datadriven.com.au
Received on Friday, 8 August 2008 05:05:38 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:27 GMT