hi:
I would like to ask you some questions about multimedia content encoding.
In the "8.5 Multipart Data" section of WAP-203-document , refer to the structure of MMS Body,but I still cann't find their specific coding.
for exmaple(How_to_create_MMS_services （http://www.forum.nokia.com/）):
0060: 3C30 3030 303E 0007 2385 1D61 7070 6C69
0070: 6361 7469 6F6E 2F73 6D69 6C00 436F 6E74
0080: 656E 742D 4944 003C 3030 3030 3E00 3C73
0090: 6D69 6C20 786D 6C6E 733D 2268 7474 703A
00A0: 2F2F 7777 772E 7733 2E6F 7267 2F32 3030
00B0: 312F 534D 494C 3230 2F4C 616E 6775 6167
00C0: 6522 3E0D 0A20 203C 6865 6164 3E0D 0A20
00D0: 2020 203C 6C61 796F 7574 3E0D 0A20 2020
00E0: 2020 203C 726F 6F74 2D6C 6179 6F75 7420
00F0: 7769 6474 683D 2231 3630 2220 6865 6967
0100: 6874 3D22 3134 3022 2F3E 0D0A 2020 2020
0110: 2020 3C72 6567 696F 6E20 6964 3D22 496D
0120: 6167 6522 2077 6964 7468 3D22 3136 3022
0130: 2068 6569 6768 743D 2231 3230 2220 6C65
0140: 6674 3D22 3022 2074 6F70 3D22 3022 2F3E
0150: 0D0A 2020 2020 2020 3C72 6567 696F 6E20
0160: 6964 3D22 5465 7874 2220 7769 6474 683D
0170: 2231 3630 2220 6865 6967 6874 3D22 3230
0180: 2220 6C65 6674 3D22 3022 2074 6F70 3D22
0190: 3132 3022 2F3E 0D0A 2020 2020 3C2F 6C61
01A0: 796F 7574 3E0D 0A20 203C 2F68 6561 643E
01B0: 0D0A 0D0A 2020 3C62 6F64 793E 0D0A 2020
01C0: 2020 3C70 6172 2064 7572 3D22 3573 223E
0000: 8C80 9830 3132 3334 3536 3738 3900 8D90
0010: 8910 802B 3132 332F 5459 5045 3D50 4C4D
0020: 4E00 972B 3435 362F 5459 5045 3D50 4C4D
0030: 4E00 964D 7920 6669 7273 7420 7465 7374
"Message Body
The next byte (07h) indicates that the multipart message body in this example consists of seven parts.
Each of the parts follows the pattern of: <length of content-type + other possible headers>, <length of data>, <content-type + other possible headers>, <data>. We’ll look at the first part in detail, so you can get an idea of how this works.
The first part starts at position 0068, which is 23h, so the content-type + other possible headers will be 23h, or 35 bytes long. Next is 85h and 1Dh. These are a long integer. The most significant bits are not used, and the rest of the bits are concatenated to get the intended value 29Dh – this indicates the length of the data. The next 35 bytes should contain the content-type, and possibly other headers. The content-type is not one with a defined WSP encoding, so it is expressed as text, “application/smil”. At this point the 35 bytes has not been completely used, so there are more headers. The next header is in plain text: “Content-ID”, and its value is at position 0087: <0000>. The actual data extends from position 008E to position 032A (29Dh bytes total)."