W3C home > Mailing lists > Public > public-device-apis@w3.org > April 2010

RE: ACTION-161 - proposal for message management

From: Suresh Chitturi <schitturi@rim.com>
Date: Tue, 27 Apr 2010 12:22:53 -0500
Message-ID: <D37CC1B151BD57489F4F89609F168FE80538B8BD@XCH01DFW.rim.net>
To: "Max Froumentin" <maxfro@opera.com>, <public-device-apis@w3.org>
Thanks Max, for the update.
Since we are trying to enhance the current draft, I'd prefer that we
take into account some of my previous comments as well (that were not
incorporated in completeness) before we go to FPWD.

I'll try to put together a proposal and send it for review this week,
using the current draft as the basis.

Some comments below.


-----Original Message-----
From: public-device-apis-request@w3.org
[mailto:public-device-apis-request@w3.org] On Behalf Of Max Froumentin
Sent: Thursday, April 22, 2010 8:31 AM
To: public-device-apis@w3.org
Subject: ACTION-161 - proposal for message management

Here's a simple solution.

add to interface MessagingManager

const unsigned short FOLDER_INBOX = 0;
const unsigned short FOLDER_OUTBOX = 1;
const unsigned short FOLDER_SENT = 2;
const unsigned short FOLDER_DRAFTS = 2;

Message[] getMessages(folder, successCB, failureCB);

add to interface Message (or just IncomingMessage, as of ACTION-142 

void delete(successCB, failureCB);

Suresh>> Assuming delete applies to all messages (e.g. incoming,
outgoing, draft) it is better to put on interface Message. What about

That covers the basic functionality. Next steps:

- filtering in getMessages() so that at least SMS, MMS, Email can be 

- any number of folders, identified by strings. And with extra functions

on IncomingMessage:

void copyTo(folder, success, failure)
void moveTo(folder, success, failure)


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 Tuesday, 27 April 2010 17:23:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:19 UTC