W3C home > Mailing lists > Public > public-dap-commits@w3.org > July 2011

2009/dap/messaging Overview.html,1.48,1.49

From: Dominique Hazael-Massieux via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 04 Jul 2011 13:06:29 +0000
To: public-dap-commits@w3.org
Message-Id: <E1Qdir7-0007Mf-ME@lionel-hutz.w3.org>
Update of /sources/public/2009/dap/messaging
In directory hutz:/tmp/cvs-serv28291

Modified Files:
	Overview.html 
Log Message:
added note on navigator.sendMessage


Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/messaging/Overview.html,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -d -r1.48 -r1.49
--- Overview.html	4 Jul 2011 12:59:44 -0000	1.48
+++ Overview.html	4 Jul 2011 13:06:27 -0000	1.49
@@ -101,7 +101,7 @@
          
          <p>Since the implications of sending a given message may depend on the message attributes (e.g. destination address) and content, the approach used to ensure user’s consent should include the relevant information, typically the type of message and its destination address.</p>
 	 <p>A typical (but not required) way of ensuring user’s consent would be to use the same mechanism as the one used when the user click on a link using one the relevant URI schemes, for instance, bringing up the platform messaging application with pre-filled fields and pre-defined attachments.</p>
-         <p>In general, user’s consent is expected to be confirmed for each invocation of the <code>sendMessage</code> methods. Typically, the user agent would bring forward the application responsible for editing/sending the type of message with pre-filled entries, allowing the user to send the message through the said application (after edits if she wants so).</p>
+         <p>In general, user’s consent is expected to be confirmed for each invocation of the <code>sendMessage</code> methods. Typically, the user agent would bring forward the application responsible for editing/sending the type of message with pre-filled entries, allowing the user to send the message through the said application (after edits if she wants so.)</p>
       </section>
  
 
@@ -120,10 +120,10 @@
 	<section>
     	<h1>API Description</h1>
       	<section>
-			<h2> <a>DeviceMessaging</a> </h2>
+			<h2> <a>NavigatorMessaging</a> </h2>
 			<p>
-				The <a href='#devicemessaging'>DeviceMessaging</a> object is exposed on the <code>navigator</code> object</p>
-
+				The <a>NavigatorMessaging</a> object is exposed on the <code>navigator</code> object</p>
+			<p class="note"><code>navigator.sendMessage</code> is a strawman proposal at this time. Further investigation on possible clash with existing code is still needed.</p>
 			
 			<div class='idl' title='Navigator implements NavigatorMessaging'></div>
 					
Received on Monday, 4 July 2011 13:06:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 4 July 2011 13:06:30 GMT