|
1 <?xml version="1.0" encoding="utf-8"?> |
|
2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. --> |
|
3 <!-- This component and the accompanying materials are made available under the terms of the License |
|
4 "Eclipse Public License v1.0" which accompanies this distribution, |
|
5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". --> |
|
6 <!-- Initial Contributors: |
|
7 Nokia Corporation - initial contribution. |
|
8 Contributors: |
|
9 --> |
|
10 <!DOCTYPE concept |
|
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
|
12 <concept id="GUID-0EDFDB1E-B851-5871-B235-453A2B2F6BFB" xml:lang="en"><title>MMS |
|
13 Settings Overview</title><prolog><metadata><keywords/></metadata></prolog><conbody> |
|
14 <p>MMS Settings provides a generic way to store settings for Multimedia Message |
|
15 Service (MMS) messaging. </p> |
|
16 <p>Multimedia Messaging Service (MMS) is a standard for telephone messaging |
|
17 systems for sending messages that include multimedia objects (images, audio, |
|
18 video, rich text). </p> |
|
19 <section><title>Purpose</title> <p>Settings functionality is provided by the <filepath>mmsgenericsettings.dll</filepath> file |
|
20 to allow a messaging client to persist MMS settings in the Central Repository. |
|
21 The settings functionality is also used by the Server MTM to retrieve the |
|
22 setting information before sending and receiving messages. </p> </section> |
|
23 <section><title>Key terms</title> <dl> |
|
24 <dlentry> |
|
25 <dt>IAP</dt> |
|
26 <dd><p>Internet Access Point (IAP) offers dial-up access to Internet. </p> </dd> |
|
27 </dlentry> |
|
28 <dlentry> |
|
29 <dt>WAP</dt> |
|
30 <dd><p>Wireless Application Protocol (WAP) is a secure specification that |
|
31 allows users to access information instantly through handheld wireless devices |
|
32 such as mobile phones. </p> </dd> |
|
33 </dlentry> |
|
34 <dlentry> |
|
35 <dt>WSP</dt> |
|
36 <dd><p>Wireless Session Protocol (WSP) provides the upper-level application |
|
37 layer of WAP with a consistent interface for connection-mode session service |
|
38 and connectionless session service. </p> </dd> |
|
39 </dlentry> |
|
40 <dlentry> |
|
41 <dt>Central Repository</dt> |
|
42 <dd><p>The Central Repository provides a user interface to allow one or more |
|
43 clients to open repositories, and to provision and retrieve information from |
|
44 those repositories. </p> </dd> |
|
45 </dlentry> |
|
46 </dl> </section> |
|
47 <section><title>Description</title> <p>The <filepath>mmsgenericsettings.dll</filepath> file |
|
48 provides message settings encapsulation classes to manage MMS settings. The |
|
49 MMS settings are stored in the central repository and MMS are stored in the |
|
50 Message Store. </p> <p>The following settings are supported by <filepath>mmsgenericsettings.dll</filepath> to |
|
51 manage MMS settings: </p> <ul> |
|
52 <li id="GUID-A505F5BF-6604-520F-9B22-63404BD04F2D"><p>MMSC (MMS server) address </p> </li> |
|
53 <li id="GUID-6F7A3C4D-36BD-5AD6-A892-0713D95D18AB"><p>WSP or HTTP transport |
|
54 (the HTTP or WSP transport can be selected at the run-time). </p> </li> |
|
55 <li id="GUID-6515A2F5-9DE3-58D3-B64C-F2424ACD90FF"><p>Automatically get messages |
|
56 on notification </p> </li> |
|
57 <li id="GUID-22EDBCFF-861F-5C59-9143-575F23DDB79B"><p>Request delivery reports </p> </li> |
|
58 <li id="GUID-C62BC75D-DAE8-51E9-8097-24D2A76DF513"><p>Preferred IAP for the |
|
59 MMS network connection </p> <p>If connection fails with the preferred IAP |
|
60 or WAP account, a connection using the second choice option, if present, is |
|
61 made. The transport selection (WSP or HTTP) determines whether the WAP or |
|
62 HTTP account preferences are applied. </p> </li> |
|
63 </ul> </section> |
|
64 <section><title>API summary</title> <p>The following APIs are used for MMS |
|
65 settings: </p> <ul> |
|
66 <li id="GUID-A83F08BF-9443-5264-BFA7-94B0CB3511BD"><p>The <xref href="GUID-45F828BF-DC03-3C82-89B5-010687BDE91D.dita"><apiname>CMmsAccounts</apiname></xref> class |
|
67 is used to store and restore the configuration settings. </p> </li> |
|
68 <li id="GUID-5D775323-165D-539F-AF3A-9E6458C60E90"><p>The <xref href="GUID-1E1BA9E3-52E1-3AE6-BC62-3EBDA577107F.dita"><apiname>CMmsSettings</apiname></xref> class |
|
69 is used to specify and retrieve configuration settings. Messaging clients |
|
70 must use an instance of this class along with the <xref href="GUID-45F828BF-DC03-3C82-89B5-010687BDE91D.dita"><apiname>CMmsAccounts</apiname></xref> class |
|
71 to store and restore the configuration settings. </p> </li> |
|
72 <li id="GUID-8D4045E2-B720-5E15-A929-750054FB5226"><p>The <xref href="GUID-C79B080E-8BE7-3126-93B9-BA59B90C2200.dita"><apiname>MMmsSettingsObserver</apiname></xref> class |
|
73 is used to provide the interface for notification of changes that occur in |
|
74 the Central Repository. </p> </li> |
|
75 </ul> <p><b> Message encapsulation </b> </p> <p>The classes above provide |
|
76 message access functionality which is used to create, store, restore and read |
|
77 messages. The following are the functions of the message classes: </p> <ul> |
|
78 <li id="GUID-A3DF991D-2A3E-5B39-ACBF-EC9F8F651CC1"><p>Adding media objects |
|
79 to the message. </p> </li> |
|
80 <li id="GUID-AA60377A-0656-56F3-9962-468DD6ED6CB1"><p>Enumerating through |
|
81 media objects. </p> </li> |
|
82 <li id="GUID-8C5AB526-139C-5F07-90E1-CBC40DB962D8"><p>Adding recipients and |
|
83 a subject line to a message. </p> </li> |
|
84 <li id="GUID-07D074D7-A3E4-59EF-9BAD-E7B1FB47435B"><p>Adding other headers |
|
85 to the message. For example, expiry date. </p> </li> |
|
86 <li id="GUID-9365FAB8-5F61-510D-9FBA-3CB14B06E5DD"><p>Finding the appropriate |
|
87 media object for a given Uniform Resource Identifier (URI) in the Synchronized |
|
88 Multimedia Integration Language (SMIL). </p> </li> |
|
89 </ul> <p>The message data is stored in the central repository using one entry |
|
90 per message regardless of the number of media objects added to the message. |
|
91 This is preferable to using multiple message entries as it is faster and uses |
|
92 less disk space. </p> </section> |
|
93 </conbody></concept> |