MMS Settings provides a generic way to store settings for Multimedia Message Service (MMS) messaging.
Multimedia Messaging Service (MMS) is a standard for telephone messaging systems for sending messages that include multimedia objects (images, audio, video, rich text).
Settings functionality is provided by the mmsgenericsettings.dll file
to allow a messaging client to persist MMS settings in the Central Repository.
The settings functionality is also used by the Server MTM to retrieve the
setting information before sending and receiving messages.
Internet Access Point (IAP) offers dial-up access to Internet.
Wireless Application Protocol (WAP) is a secure specification that allows users to access information instantly through handheld wireless devices such as mobile phones.
Wireless Session Protocol (WSP) provides the upper-level application layer of WAP with a consistent interface for connection-mode session service and connectionless session service.
The Central Repository provides a user interface to allow one or more clients to open repositories, and to provision and retrieve information from those repositories.
The mmsgenericsettings.dll file
provides message settings encapsulation classes to manage MMS settings. The
MMS settings are stored in the central repository and MMS are stored in the
Message Store.
The following settings are supported by mmsgenericsettings.dll to
manage MMS settings:
MMSC (MMS server) address
WSP or HTTP transport (the HTTP or WSP transport can be selected at the run-time).
Automatically get messages on notification
Request delivery reports
Preferred IAP for the MMS network connection
If connection fails with the preferred IAP or WAP account, a connection using the second choice option, if present, is made. The transport selection (WSP or HTTP) determines whether the WAP or HTTP account preferences are applied.
The following APIs are used for MMS settings:
The CMmsAccounts class
is used to store and restore the configuration settings.
The CMmsSettings class
is used to specify and retrieve configuration settings. Messaging clients
must use an instance of this class along with the CMmsAccounts class
to store and restore the configuration settings.
The MMmsSettingsObserver class
is used to provide the interface for notification of changes that occur in
the Central Repository.
Message encapsulation
The classes above provide message access functionality which is used to create, store, restore and read messages. The following are the functions of the message classes:
Adding media objects to the message.
Enumerating through media objects.
Adding recipients and a subject line to a message.
Adding other headers to the message. For example, expiry date.
Finding the appropriate media object for a given Uniform Resource Identifier (URI) in the Synchronized Multimedia Integration Language (SMIL).
The message data is stored in the central repository using one entry per message regardless of the number of media objects added to the message. This is preferable to using multiple message entries as it is faster and uses less disk space.