| Confused about the header field name assignment (ex/. content-type)... |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Leonard Chen |
Hi, I'm confused about some well-known header field name assignments in MMS. Since the MMS payload is transfered by WSP, the header field is assumed using WSP's assignment. For example, 'Content-Type's assigned number is 0x11 in WAP203. But the WAP209 defines another number of 0x04 for it. So, what's the difference between WAP209's assigned number and that of WAP203's ? and which one should be used? Thanx first Liang | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Liang, Yes, this is all very confusing. But basically, there are different binary encoding mappings for different message constructs. WAP-209 documents the binary MMS message format (application/vnd.wap.mms-message). This message tends to be transported inside of a WSP message, so the actual transported message has a WSP header preceding the MMS message content. Then once you have left the WSP header, and moved into the MMS message, it has a header of its own, and it's header encoding format is defined by WAP-209. What then makes things more confusing, is that beyond the header of the MMS message, the MMS content itself is represented using application/vnd.wap.mulipart.* encoding, which is defined WSP. Individual parts of the multipart content have headers of their own, and those headers are encoding using WSP header encoding format. Kind of amazing that it can all work in the real world.  -bn | |||
| Leonard Chen |
Oh, maybe the MMS initiator feels unhappy with WSP :-) Many thanks for your help! Best Regards, Liang | |||
