HP-UX C SIP Stack Programmer's Guide (Novembery 2007)

Working with SIP Messages 175
Working With Multipart MIME
The SIP Stack Message API provides a set of functions that enables you to
Construct, Parse and encode multipart MIME bodies.
MESSAGE MULTIPART
B
ODY STRUCTURE
The SIP Stack provides two types of objects for working with multipart MIME
bodies—the Body object and the Body Part objects. Both the Body and the
Body Part objects are identified using handles.
Similar to the Message API, when you construct a Body or Body Part object, the
Construct() function returns the handle to the newly created object. Whenever
performing an operation on the object, you must supply the object handle to the
function.
B
ODY OBJECT The Body object is identified using the RvSipBodyHandle. Each SIP message
can hold only one Body object. A Body object includes the following elements
(each of them may be empty):
 Content-Type header—defines the type of the Body, such as
multipart MIME.
 Body string—a buffer that holds the Body information (textual
or binary).
 List of Body Parts—when the Body is of type multipart MIME,
it can hold a list of Body Parts instead of a Body string.
B
ODY PART OBJECT The Body Part object is identified using the RvSipBodyPartHandle. A Body
Part object includes the following elements (each of them can be empty):
 Headers list
 Content Disposition header
 Body object.
Note The Body and Body Part objects are defined recursively within one
another.