Java Reference
In-Depth Information
only has a limited number of headers that are defined by the protocol specification.
Table 14-2 shows the most common headers and their purpose. Note that a specific
message might not bear all of these headers or might bear additional headers not shown
in Table 14-2.
Table 14-2.
Common MultipartMessage Headers and Their Meaning
Header Name
Purpose
X-Mms-Delivery-Time
The date and time at which the message must be delivered to the
recipient
X-Mms-Expiry
The date and time at which the message should expire and not be
delivered by the MMSC
X-Mms-Message-Class
The class of message—either
Personal
,
Advertisement
,
Informational
, or
Auto
X-Mms-Priority
The priority of the message—either
High
,
Normal
, or
Low
X-Mms-Transaction-Id
The assigned transaction ID for the message
■
Note
The MMS protocol underlying the
MultipartMessage
is specified by the Open Mobile
Alliance (OMA) and its WAP-209-MMSEncapsulation standard. If you're going to work deeply with the
MultipartMessage
class and the MMS protocol, it's a good idea to closely read this and other MMS
documentation at the OMA web site (
http://www.openmobilealliance.org
). JSR 205 cites this
standard; Appendix D of JSR 206 discusses how the MMS message structure that the OMA defines maps
to the interfaces that the WMA provides.
Understanding Required Privileges When Using the WMA
Just as when using the GCF for HTTP or socket requests, using the GCF to obtain a
MessageConnection
instance requires privilege. The WMA defines the following privileges
for each kind of message it supports:
•
javax.microedition.io.Connector.sms
: Required to obtain a
MessageConnection
that
can send or receive text or binary SMS messages
•
javax.microedition.io.Connector.cbs
: Required to obtain a
MessageConnection
that
can receive SMS-CB messages
•
javax.microedition.io.Connector.mms
: Required to obtain a
MessageConnection
that
can send or receive MMS messages
