Should profile header be packed in the WSP layer? | Search |
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
Author | Message | |||
Anonymous |
in the wap-230-wsp.pdf, it says compact encodings are defined for the well-known headers to reduce protocol overhead in the section 5.2.1 and in the section 8.4 Header encoding it says the field name could be binary /text format or integer value depending on the encoding version. | |||
Bryce Norwood - NowSMS Support |
Are you asking if the "Profile:" header itself should be binary encoded? If so, then from experience, I have seen that it generally is encoded. | |||
Anonymous |
any other headers should be send in the mms get packet?thanks it's better if you would afford me a example of the format t of he packet | |||
Bryce Norwood - NowSMS Support |
I'd leave it to a line analyser like Ethereal to capture a packet. Generally the only header you would need to be concerned with is the "Accept:" header. You need to tell the WAP gateway and the content server (MMSC) that you will accept the "application/vnd.wap.mms-message" MIME type. In practice, you'd probably include the "Profile:" header and the "Accept:" header in the WSP CONNECT. Any headers specified in the "Connect" apply for the duration of the session. I think it is still a good idea to include the "Accept:" header in the GET request as well. There are a lot of different WAP gateways out there, and it is important that this header gets through, so personally, I like the idea of explicitly including it in the GET request. -bn |