- From: Richard Tibbett via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 11 Jan 2011 15:05:01 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/calendar
In directory hutz:/tmp/cvs-serv8072/calendar
Modified Files:
Overview.html
Log Message:
Added Event loop details for asynchronous callbacks.
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/calendar/Overview.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -d -r1.13 -r1.14
--- Overview.html 11 Jan 2011 14:47:43 -0000 1.13
+++ Overview.html 11 Jan 2011 15:04:59 -0000 1.14
@@ -252,7 +252,35 @@
</section> -->
-
+ <section>
+ <h2>
+ Terminology
+ </h2>
+ <p>
+ The terms <dfn>document base URL</dfn>, <dfn>browsing context</dfn>, <dfn
+ title="event handler attribute">event handler attributes</dfn>, <dfn>event handler event type</dfn>, <dfn>task</dfn>, <dfn>task
+ source</dfn> and <dfn>task queues</dfn> are defined by the HTML5 specification [[!HTML5]].
+ </p>
+ <p>
+ The <a>task source</a> used by this specification is the <dfn><a
+ href="http://dev.w3.org/2009/dap/device/#the-pendingop-interface">PendingOp</a> task source</dfn>.
+ </p>
+
+ <p class="note">
+ PendingOp needs updating in [[!CORE-DEVICE]] to show that it is a valid <a>task source</a>.
+ </p>
+ <p>
+ To <dfn>dispatch a <code>success</code> event</dfn> means that an event with the name <code>success</code>, which does
+ not bubble and is not cancelable, and which uses the <code>Event</code> interface, is to be dispatched at the <a
+ href="#contactfindcb-interface"><code>ContactFindCB</code></a> object.
+ </p>
+ <p>
+ To <dfn>dispatch an <code>error</code> event</dfn> means that an event with the name <code>error</code>, which does
+ not bubble and is not cancelable, and which uses the <code>Event</code> interface, is to be dispatched at the <a
+ href="#contacterrorcb-interface"><code>ContactErrorCB</code></a> object.
+ </p>
+ </section>
+
</section>
<section class="informative">
@@ -414,14 +442,25 @@
<p>This method takes two, three or four arguments. When called, it must immediately return
a <code>PendingOp</code> object, as defined in [[!CORE-DEVICE]] and then asynchronously start a <dfn>find calendar event items</dfn> process defined as follows:</p>
- <p>
- <ol>
- <li>Search for calendar event items in the calendar according to the <a href='#calendar-item-search-processing-rules'>calendar item search processing rules</a>.</li>
- <li>If successful, invoke the associated <code>successCB</code>.
- If the attempt fails, and the method was invoked with a non-null <code>errorCB</code> argument, this method must
- invoke the <code>errorCB</code> with a <a href='#calendarerror-interface'><code>CalendarError</code></a> object as an argument.</li>
- </ol>
- </p>
+ <ol
+ class="rule">
+ <li>
+ If there are any <a>tasks</a> from the <a
+ title="PendingOp task source"><code>PendingOp</code> task source</a> in one of the <a>task queues</a>
+ (i.e. an existing <code>find()</code> operation is still pending a response), and the current method was invoked with a
+ non-<code>null</code> <code>errorCB</code> argument, <a>dispatch an <code>error</code> event</a> with a <a
+ href='#widl-CalendarError-PENDING_OPERATION_ERROR'><code>PENDING_OPERATION_ERROR</code></a> <code>code</code> value.
+ </li>
+ <li>
+ Search for calendar event items in the calendar according to the
+ <a href='#calendar-item-search-processing-rules'>calendar item search processing rules</a>.
+ </li>
+ <li>
+ If the attempt was successful, <a>dispatch a <code>success</code> event</a>. If the attempt fails, and the method was
+ invoked with a non-<code>null</code> <code>errorCB</code> argument, this method must <a>dispatch an <code>error</code>
+ event</a> with the <code>code</code> attribute set according to the type of failure that has occurred.
+ </li>
+ </ol>
<dl class='parameters'>
<dt>
@@ -829,7 +868,41 @@
</dd>
</dl>
</dd>
- </dl>
+ </dl>
+
+ <section>
+ <h3>
+ Event Handler Attributes
+ </h3>
+ <p>
+ The following is the <a>event handler attribute</a> (and its corresponding <a>event handler event type</a>) that MUST be
+ supported as a DOM attribute by the <a
+ href="#calendareventsuccesscb-interface"><code>CalendarEventSuccessCB</code></a> object.
+ </p>
+ <table
+ class='simple'>
+ <thead>
+ <tr>
+ <th>
+ <a>event handler attribute</a>
+ </th>
+ <th>
+ <a>event handler event type</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ <strong><code><strong>onsuccess</strong></code></strong>
+ </td>
+ <td>
+ <code>success</code>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
</section>
<section>
@@ -854,6 +927,40 @@
</dl>
</dd>
</dl>
+
+ <section>
+ <h3>
+ Event Handler Attributes
+ </h3>
+ <p>
+ The following is the <a>event handler attribute</a> (and its corresponding <a>event handler event type</a>) that MUST be
+ supported as a DOM attribute by the <a
+ href="#calendarerrorcb-interface"><code>CalendarErrorCB</code></a> object.
+ </p>
+ <table
+ class='simple'>
+ <thead>
+ <tr>
+ <th>
+ <a>event handler attribute</a>
+ </th>
+ <th>
+ <a>event handler event type</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>
+ <strong><code><strong>onerror</strong></code></strong>
+ </td>
+ <td>
+ <code>error</code>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
</section>
Received on Tuesday, 11 January 2011 15:05:03 UTC