Table of Contents
Advertisement
others are specific to multimedia messaging. In addition to defined MMS headers, it also
contains header parameters as defined by JSR 205. The message body may contain
parts of any content type and MIME multipart is used to represent and encode a wide
variety of media types for transmission via multimedia messaging.
MMS Message Addressing
The multipart message addressing model contains different types of addresses:
The syntax of the URL connection strings SHALL follow the rules specified in Table D-2 of
JSR- 205 specification.
MMS Message Types
MMS messages can be sent using MULTIPART_MESSAGE type of this API. The default
type of message is multipart/related. If the content type header does not contain start
parameter, the message type is asumed to be multipart/mixed. This section describes
Multipart Message, and its related classes. Messaging framework is described in the JSR
120 chapter of this developer guide.
MultipartMessage
The WMA shall implement the MultipartMessage an interface representing a multipart
message. This is a sub interface of Message which contains methods to add, remove and
manipulate message parts. The interface also allows to specify the subject of the
message.
Please refer JSR 205 specification for more details.
MessagePart
The WMA shall implement the MessagePart a class representing a media part that can be
sent with the message. Instances of MessagePart class are added to the
MultipartMessage.
Each message part consists of part header and part body. The part headers include
Content ID, Content Location, Content type, Encoding scheme. Content can be of any
MIME type.
32
•
global telephone number of recipient user, including telephone number,
ipv4, ipv6 adresses
•
e-mail address as specified in RFC822
•
short-code of the service (not valid for MMS version 1.0)
Advertisement
Table of Contents
