Confirmed users
398
edits
Line 29: | Line 29: | ||
MessagingRequest markMessageRead (DOMString id, boolean value); | MessagingRequest markMessageRead (DOMString id, boolean value); | ||
MessagingRequest markConversationRead (DOMString id, boolean value); | MessagingRequest markConversationRead (DOMString id, boolean value); | ||
MessagingRequest addArrivedMessage( | MessagingRequest addArrivedMessage(MmsMessage msg); // IM or Telephony Apps can add a new message as a new arrival. | ||
}; | }; | ||
Line 42: | Line 42: | ||
addArrivedMessage() is added to Messaging to let communication Apps add a message for a new arriving message. |handler| is added to Message to record the application can handle replying the message. |receiver| is the account receiving the message. It is used by the handler to distinguish the user of the service. The message app is not supposed for responding for editing messages. It should wake up the handler of the message for editing. |type| and |serviceID| can be removed and replaced by |handler| and |receiver| while |receiver| are used to distinguish different SIM. | addArrivedMessage() is added to Messaging to let communication Apps add a message for a new arriving message. |handler| is added to Message to record the application can handle replying the message. |receiver| is the account receiving the message. It is used by the handler to distinguish the user of the service. The message app is not supposed for responding for editing messages. It should wake up the handler of the message for editing. |type| and |serviceID| can be removed and replaced by |handler| and |receiver| while |receiver| are used to distinguish different SIM. | ||
MmsMessage are suggested for more flexible that handler can format the message in HTML to provide a rich representation. | |||
Should we provide a way for synchronization between the database of Messaging API and App's local storage? | Should we provide a way for synchronization between the database of Messaging API and App's local storage? |