Skip to content
This repository was archived by the owner on Oct 2, 2019. It is now read-only.

Commit 03a15f3

Browse files
author
Eduardo Fullea
committed
System Messages to wake up the app if not running
1 parent e47c108 commit 03a15f3

File tree

1 file changed

+84
-0
lines changed

1 file changed

+84
-0
lines changed

index.html

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -698,6 +698,10 @@ <h3>Steps</h3>
698698
<li><a>Queue a task</a> to <a>fire an event</a> named
699699
<code><a>received</a></code> with the <code>message</code> attribute set
700700
to the newly created <code>SmsMessage</code> instance.
701+
<li><a>Queue a task</a> to fire a system message named
702+
<code>received</code> of type <code><a>ReceivedMessage</a></code> with the
703+
<code>message</code> attribute set to the newly created
704+
<code>SmsMessage</code> instance.
701705
</ol>
702706

703707
<p>Upon a delivery report of a previously sent SMS message being received, the
@@ -717,6 +721,18 @@ <h3>Steps</h3>
717721
<li>the <code>recipients</code> attribute set to the recipient of such
718722
message.
719723
</ol>
724+
<li><a>Queue a task</a> to fire a system message of type
725+
<code><a>DeliveryReport</a></code>named <a>deliverysuccess</a> or
726+
<a>deliveryfailure</a> respectively if the delivery was successfull or
727+
not, with
728+
<ol>
729+
<li>the <code>messageID</code> attribute set to the identifier of the
730+
<code>SmsMessage</code> to which this confirmation is related,
731+
<li>the <code>serviceID</code> attribute set to the identifier of the
732+
service used to send such message, and
733+
<li>the <code>recipients</code> attribute set to the recipient of such
734+
message.
735+
</ol>
720736
</ol>
721737

722738
<p> The <dfn><code>clear</code></dfn> method when invoked MUST run the
@@ -1149,6 +1165,10 @@ <h3>Steps</h3>
11491165
<li><a>Queue a task</a> to <a>fire an event</a> named
11501166
<code><a>received</a></code> with the <code>message</code> attribute set
11511167
to the newly created <code>MmsMessage</code> instance.
1168+
<li><a>Queue a task</a> to fire a system message named
1169+
<code>received</code> of type <code><a>ReceivedMessage</a></code> with the
1170+
<code>message</code> attribute set to the newly created
1171+
<code>MmsMessage</code> instance.
11521172
</ol>
11531173
</ol>
11541174

@@ -1224,6 +1244,18 @@ <h3>Steps</h3>
12241244
<li>the <code>recipients</code> attribute set to the subset of the
12251245
original recipients to which this delivery report is related.
12261246
</ol>
1247+
<li><a>Queue a task</a> to fire a system message of type
1248+
<code><a>DeliveryReport</a></code>named <a>deliverysuccess</a> or
1249+
<a>deliveryfailure</a> respectively if the delivery was successfull or
1250+
not, with
1251+
<ol>
1252+
<li>the <code>messageID</code> attribute set to the identifier of the
1253+
<code>MmsMessage</code> to which this confirmation is related,
1254+
<li>the <code>serviceID</code> attribute set to the identifier of the
1255+
service used to send such message, and
1256+
<li>the <code>recipients</code> attribute set to the recipient of such
1257+
message.
1258+
</ol>
12271259
</ol>
12281260

12291261
<p> The <dfn><code>clear</code></dfn> method when invoked MUST run the
@@ -1680,6 +1712,58 @@ <h2><a>MessagingCursor</a> Interface</h2>
16801712
</section>
16811713

16821714

1715+
<!------------------------ Interface ReceivedMessage ------------------------->
1716+
<section>
1717+
<h2><a>ReceivedMessage</a> Interface</h2>
1718+
<p>The <a>ReceivedMessage</a> interface represents a system message related to
1719+
a received message. This event is originated from the system and will wake up
1720+
the application if it is not currently running.
1721+
1722+
<p>The application that consumes this API SHOULD set a message handler for the
1723+
<code>ReceivedMessage</code> system message to listen for when a system
1724+
message related to a received message is fired.
1725+
1726+
<dl title="interface ReceivedMessage"
1727+
class="idl">
1728+
<dt>readonly attribute (SmsMessage or MmsMessage) message</dt>
1729+
<dd>MUST return the <code>SmsMessage</code> or <code>MmsMessage</code>
1730+
object to which this system message is related.</dd>
1731+
</dl>
1732+
</section>
1733+
1734+
1735+
<!------------------------ Interface DeliveryReport -------------------------->
1736+
<section>
1737+
<h2><a>DeliveryReport</a> Interface</h2>
1738+
<p>The <a>DeliveryReport</a> interface represents a system message related to
1739+
a delivery report of a sent message. This event is originated from the system
1740+
and will wake up the application if it is not currently running.
1741+
1742+
<p>The application that consumes this API MAY set a message handler for the
1743+
<code>DeliveryReport</code> system message to listen for when a system
1744+
message related to a received delivery report is fired.
1745+
1746+
<dl title="interface DeliveryReport"
1747+
class="idl">
1748+
<dt>readonly attribute DOMString serviceID</dt>
1749+
<dd>MUST return the identifier of the service used to send the message to
1750+
which this delivery report is related.</dd>
1751+
<dt>readonly attribute DOMString messageID</dt>
1752+
<dd>MUST return the identifier of the message to which this delivery
1753+
report is related.</dd>
1754+
<dt>readonly attribute DOMString[] recipients</dt>
1755+
<dd>MUST return an array contining the addresses of the subset of the
1756+
original recipients of the message to which this delivery report is
1757+
related. As delivery reports related to just part of the recipients of the
1758+
MMS message are possible, this array may not contain the full list of
1759+
recipients to which the MMS message was sent. If the delivery report is
1760+
related to an SMS message then the array will contain a single element
1761+
corresponding to the single recipient of the SMS message.
1762+
</dd>
1763+
</dl>
1764+
</section>
1765+
1766+
16831767
<!------------------------ Interface MessagingEvent -------------------------->
16841768
<section>
16851769
<h2><a>MessagingEvent</a> Interface</h2>

0 commit comments

Comments
 (0)