Confirmed users
716
edits
WebAPI/WebSMS: Difference between revisions
Jump to navigation
Jump to search
→Proposed API
| Line 19: | Line 19: | ||
interface SmsManager | interface SmsManager | ||
{ | { | ||
SmsRequest send( | SmsRequest send(DOMString number, DOMString message); | ||
SmsRequest[] send(DOMString[] number, DOMString message); | |||
unsigned short getNumberOfMessagesForText(in DOMString text); | unsigned short getNumberOfMessagesForText(in DOMString text); | ||
SMSRequest delete(in long | SMSRequest delete(in long id); | ||
SMSRequest delete(in SmsMessage message); | SMSRequest delete(in SmsMessage message); | ||
SMSRequest getMessage(in long | SMSRequest getMessage(in long id); // request.result == SMSMessage | ||
SMSRequest getMessages(in SMSFilter filter, bool reverse); // request.result == SMSIterator | SMSRequest getMessages(in SMSFilter filter, bool reverse); // request.result == SMSIterator | ||
}; | }; | ||
Comments: | Comments: | ||
Should use use opaque objects as message-identifiers rather than longs? | |||
interface SmsRequest | interface SmsRequest | ||
{ | { | ||
readonly attribute | readonly attribute DOMString readyState; // "processing" or "done" | ||
readonly attribute | readonly attribute DOMString? errorCode; | ||
attribute EventListener | attribute EventListener onsuccess; | ||
attribute EventListener | attribute EventListener onerror; | ||
attribute readonly | attribute readonly Object? message; | ||
}; | }; | ||
interface SmsMessage | interface SmsMessage | ||
{ | { | ||
readonly attribute long | readonly attribute long id; | ||
readonly attribute boolean fromMe; // Terrible name! | |||
readonly attribute DOMString sender; | readonly attribute DOMString sender; | ||
readonly attribute DOMString receiver; | readonly attribute DOMString receiver; | ||