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

Commit 44c5859

Browse files
author
Eduardo Fullea
committed
Merge pull request #72 from efullea/updates
Closing #66, #67 and #69
2 parents 67af5c1 + 706f606 commit 44c5859

File tree

1 file changed

+40
-14
lines changed

1 file changed

+40
-14
lines changed

index.html

Lines changed: 40 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -856,7 +856,7 @@ <h2><a>MmsManager</a> Interface</h2>
856856

857857
<dt>FetchMode getFetchMode ()</dt>
858858
<dd>This method requests to retrieve the fetch mode associated to a specific
859-
service (the one identified by the <code>serviceID</code> attribute, if
859+
service (the one identified by the <code>serviceID</code> parameter, if
860860
provided, or the first item in the <code>serviceIDs</code> attribute of
861861
the <code>MmsManager</code> otherwise).
862862
<dl class='parameters'>
@@ -868,12 +868,10 @@ <h2><a>MmsManager</a> Interface</h2>
868868
</dd>
869869

870870
<dt>void setFetchMode ()</dt>
871-
<dd>This method issues a request to the messaging system to set to <a
872-
class="internalDFN" href="#idl-def-FetchMode.manual">manual</a>
873-
or <a class="internalDFN" href="#idl-def-FetchMode.automatic">automatic</a>
874-
the MMS message fetch mode of the specific service, the one identified by
875-
the <code>serviceID</code> attribute, if provided, or all services
876-
otherwise).
871+
<dd>This method issues a request to the messaging system to set the MMS
872+
message fetch mode for the service identified by the <code>serviceID</code>
873+
parameter, if provided, or for all services otherwise, to the mode indicated
874+
in the <code>fetchMode</code> parameter.
877875
<dl class='parameters'>
878876
<dt>FetchMode fetchMode</dt>
879877
<dd>
@@ -1078,7 +1076,10 @@ <h3>Steps</h3>
10781076
identifier of the service at which the message has been received.
10791077
<li>Set the <code>read</code> of the <code>MmsMessage</code> to 'false'.
10801078
<li>if the fetch mode is <a class="internalDFN"
1081-
href="#idl-def-FetchMode.manual">manual</a>:
1079+
href="#idl-def-FetchMode.manual">manual</a>, <a class="internalDFN"
1080+
href="#idl-def-FetchMode.never">never</a> or the device is not in the home
1081+
network and the the fetch mode is <a class="internalDFN"
1082+
href="#idl-def-FetchMode.automatic-home">automatic-home</a>:
10821083
<ol>
10831084
<li>Set the <code>from</code> of the <code>MmsMessage</code> to the
10841085
value of the 'From' field of the MMS notification, if present.
@@ -1104,7 +1105,9 @@ <h3>Steps</h3>
11041105
'not-downloaded'.
11051106
</ol>
11061107
<li>if the fetch mode is otherwise <a class="internalDFN"
1107-
href="#idl-def-FetchMode.automatic">automatic</a>:
1108+
href="#idl-def-FetchMode.automatic">automatic</a> or the device is in the
1109+
home network and the the fetch mode is <a class="internalDFN"
1110+
href="#idl-def-FetchMode.automatic-home">automatic-home</a>:
11081111
<ol>
11091112
<li>Make a request to the system to fetch the MMS message from the URL
11101113
indicated in the X-Mms-Content-Location field of the MMS notification.
@@ -1164,13 +1167,15 @@ <h3>Steps</h3>
11641167

11651168
<p> The <dfn><code>fetch</code></dfn> method can be invoked to fetch an MMS
11661169
message that has not been automatically fetched upon receiving the
1167-
corresponding MMS notification due to the fetch mode being manual. When this
1170+
corresponding MMS notification, e.g. due to the fetch mode being <a
1171+
class="internalDFN" href="#idl-def-FetchMode.manual">manual</a>. When this
11681172
method is invoked the User Agent MUST run the following steps:
11691173
<ol>
11701174
<li>If the <code>messageID</code> parameter passed in the request matches
11711175
with an MMS message that has already been fetched, or to an SMS message go
1172-
to next step, otherwise make a request to the system to fetch the MMS
1173-
message.
1176+
to next step, otherwise set the <code>state</code> of the
1177+
<code>MmsMessage</code> to 'fetching' and make a request to the system to
1178+
fetch the MMS message.
11741179
<li>Let <var>future</var> be a new <code>Future</code> object and
11751180
<var>resolver</var> its associated <code>resolver</code>
11761181
<li>Return <var>future</var> to the caller.
@@ -1380,7 +1385,7 @@ <h2><a>SmsMessage</a> Interface</h2>
13801385
<dt>readonly attribute SmsState state</dt>
13811386
<dd>MUST return the status of the SMS message.</dd>
13821387

1383-
<dt>readonly attribute DeliveryStatus? deliveryStatus</dt>
1388+
<dt>readonly attribute DeliveryStatus deliveryStatus</dt>
13841389
<dd>MUST return the delivery status of the SMS message.
13851390
</dd>
13861391

@@ -1885,10 +1890,17 @@ <h2>Enumerations</h2>
18851890
<dl class="idl" title="enum MmsState">
18861891
<dt>not-downloaded</dt>
18871892
<dd>
1888-
The message is an inbound message, for which an MMS mnotification
1893+
The message is an inbound message, for which an MMS notification
18891894
has been received but that has not yet been downloaded.
18901895
</dd>
18911896

1897+
<dt>fetching</dt>
1898+
<dd>
1899+
The message is an inbound message, for which an MMS notification
1900+
has been received, and whose download has started and not yet
1901+
finished.
1902+
</dd>
1903+
18921904
<dt>received</dt>
18931905
<dd>
18941906
The message is an inbound message.
@@ -1948,11 +1960,25 @@ <h2>Enumerations</h2>
19481960
notification.
19491961
</dd>
19501962

1963+
<dt>automatic-home</dt>
1964+
<dd>
1965+
MMS message is fecthed right after the reception of the MMS
1966+
notification if the device is located in the home network, i.e.
1967+
not roaming, otherwise the message will be fetched upon the device
1968+
entering in the home network again or the user manually requesting
1969+
it.
1970+
</dd>
1971+
19511972
<dt>manual</dt>
19521973
<dd>
19531974
The message is not fecthed until the user manually requests it.
19541975
</dd>
19551976

1977+
<dt>never</dt>
1978+
<dd>
1979+
MMS message retrieval is completely disabled.
1980+
</dd>
1981+
19561982
</dl>
19571983

19581984
</section>

0 commit comments

Comments
 (0)