- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 10 Jul 2008 01:10:41 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/workers
In directory hutz:/tmp/cvs-serv5412
Modified Files:
Overview.html
Log Message:
First pass at requirements. (whatwg r4)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/workers/Overview.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- Overview.html 9 Jul 2008 11:00:48 -0000 1.2
+++ Overview.html 10 Jul 2008 01:10:39 -0000 1.3
@@ -19,7 +19,7 @@
specification for HTML5</h2>
<h2 class="no-num no-toc" id=editors><!-- "W3C Working Draft" --> Editor's
- Draft <!--ZZZ--> 9 July 2008</h2>
+ Draft <!--ZZZ-->10 July 2008</h2>
<dl><!-- ZZZ: update the month/day
<dt>This Version:</dt>
@@ -144,8 +144,8 @@
<p>The W3C <a href="http://www.w3.org/html/wg/">HTML Working Group</a> is
the W3C working group responsible for this specification's progress along
- the W3C Recommendation track. <!--ZZZ:--> This specification is the 9 July
- 2008 <!--ZZZ "Working Draft"-->Editor's Draft. <!--:ZZZ--></p>
+ the W3C Recommendation track. <!--ZZZ:--> This specification is the 10
+ July 2008 <!--ZZZ "Working Draft"-->Editor's Draft. <!--:ZZZ--></p>
<!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST -->
<!-- relationship to other work (required) -->
@@ -183,7 +183,8 @@
<ul class=toc>
<li><a href="#background"><span class=secno>1.1 </span>Background</a>
- <li><a href="#scope"><span class=secno>1.2 </span>Scope</a>
+ <li><a href="#requirements"><span class=secno>1.2
+ </span>Requirements</a>
<li><a href="#relationships"><span class=secno>1.3 </span>Relationships
to other specifications</a>
@@ -219,10 +220,56 @@
<p><em>This section is non-normative.</em>
- <h3 id=scope><span class=secno>1.2 </span>Scope</h3>
+ <h3 id=requirements><span class=secno>1.2 </span>Requirements</h3>
<p><em>This section is non-normative.</em>
+ <p>This specification aims to address the following use cases and
+ requirements:
+
+ <ul>
+ <li>Background workers: A Web application needs to keep its data
+ synchronised with the server, both sending updates to the server and
+ receiving updates from the server, including handling buffering of
+ updates for when the application goes offline. The code to do this would
+ ideally be independent of the UI code.
+
+ <li>URLs: Workers should be spawned from URLs, not from strings, since
+ script rarely has access to its own source.
+
+ <li>Message queuing: Messages sent to a worker before the worker has
+ initialised should not be lost.
+
+ <li>Workers should have access to timers.
+
+ <li>Workers should have access to the network.
+
+ <li>Workers should be able to use libraries.
+
+ <li>Implementations should not have to expose <code>Node</code> or
+ <code>Document</code> objects to workers.
+
+ <li>Workers should not share anything with the outside world. The objects
+ representing the worker in the worker itself and in the context that
+ created the worker should be different, for instance.
+
+ <li>Shared workers: Multiple instances of the same Web application would
+ want to keep just one connection back to the server.
+
+ <li>Capabilities granting: It should be possible for code running in one
+ iframe to negotiate a connection to another iframe, with that connection
+ granting certain rights (e.g. adding to an address book but not reading
+ from it).
+
+ <li>Delegation: It should be possible for one worker to spawn another
+ worker and efficiently delagate a request to that worker, without the
+ caller being aware of the delagate and without the original worker having
+ to proxy all the messages.
+
+ <li>Workers whose parents are not longer useful should be killed. Workers
+ should be able to detect this is about to happen and exit gracefully.
+ </ul>
+
<h3 id=relationships><span class=secno>1.3 </span>Relationships to other
specifications</h3>
Received on Thursday, 10 July 2008 01:11:16 UTC