| Encoding a M-retrieve.conf message |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Craig Dunn |
Hi - appologies if this seems a lame question, but I just cant find enough available documentation on this subject to get my head around it. I understand, that an MMS message consists of a multi-part MIME message, one of which is a SMIL presentation (does it have to have a SMIL part?) and the other(s) are the image / text parts of the message. Now - I understand the various WDP/WSP encoding, and the MMS headers (http://support.nowsms.com/discus/messages/12/522.html for example) What I'm unclear on, is how the MIME / SMIL is encoded - is it just simply translated char by char into hex (including spaces, line feeds...etc) or is there some other wizardry I need to do to it first? Any example encodings, advice, tips ..etc would be most appreciated. Thanks Regards Craig Dunn | |||
| Bryce Norwood - NowSMS Support |
Craig, A SMIL file is not strictly required, but it's a good idea to include one if you can. Basically, it's up to the receiving MMS client as to how to present the received message ... and there are a few MMS compatible phones that present messages rather awkward if there is no SMIL file. The content is transferred character by character as is ... without any encoding of the actual content. The WSP multipart encoding that is used basically just performs binary encoding on the MIME headers that would appear in a multipart message ... the actual content is encoded "as is". So if the content is a text file, then it is included complete with tabs, spaces, carriage returns, line feeds, etc. If the content is binary, then it is included in its binary format (no base64 or other encoding). -bn | |||
