W3C home > Mailing lists > Public > public-device-apis@w3.org > March 2011

Re: Messaging API proposal

From: Suresh Chitturi <schitturi@rim.com>
Date: Wed, 9 Mar 2011 10:41:35 -0600
Message-ID: <D37CC1B151BD57489F4F89609F168FE809233D62@XCH01DFW.rim.net>
To: <dom@w3.org>, <public-device-apis@w3.org>
Dom,all,

I missed the discussion/call today but can both models co-exist? I hate to see us bactracking on previous assumptions without major concerns with our current approach. I think what we have is fairly simplified from where we started.

Regards,
Suresh 


----- Original Message -----
From: Dominique Hazael-Massieux [mailto:dom@w3.org]
Sent: Wednesday, March 09, 2011 10:28 AM
To: public-device-apis@w3.org <public-device-apis@w3.org>
Subject: Messaging API proposal

Hi,

As discussed on the call today [1], maybe the best way to go about the
messaging API is to make it as simple as possible by reusing as much of
the URI schemes capabilities (which already handle to/cc/body/subject
etc), and have a simple:
  navigator.sendMessage("mailto:dom@w3.org?subject=Your%20idea%20is%
20fantastic&body=We%20love%you", [Blob1, Blob2], errorCB)
where the list of Blobs would add attachments.

In WebIDL term, we would need to define a single method,  la
        caller void sendMessage (DOMString to, sequence<Blob>
        attachments, messagingErrorCB? errorCB);
and the messagingErrorCB interface.

How does that look?

Dom, for ACTION-348 and ISSUE-107

1. http://www.w3.org/2011/03/09-dap-minutes.html#item10




---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Received on Wednesday, 9 March 2011 16:43:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:18 GMT