| M-Send.req message that is not multipart |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 05, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Roland Marslin New member Username: Roolando Post Number: 1 Registered: 04-2005 |
Can an M-Send.req message contain content that is not multipart ? ie. instead of Content-type application/vnd.wap.multipart.mixed (usually encoded as 0x84 0xa3) then followed by 1 or more multipart entries; is it possible to have just a plain/text content for example: 0x84 0x83 followed by a text message ? The only examples I have seen would encode a plain/text message as a single multipart content - but is this necessary ? Can the text message be encoded without using any kind of multipart type ? If it is possible (the specifications I've read don't appear to prohibit this) how could you tell where the (non-multipart) content ends ? The only length indication would appear to be the HTTP header Content-Length. | |||
| Forest Luo New member Username: Forest_luo Post Number: 28 Registered: 04-2004 |
I think handset may only support two kinds of MMS : mixed or related. | |||
| dono Unregistered guest |
I've seen one NEC phone model which doesn't use both mixed or related when sending only TEXT in MMS message (single part). It has text/plain as Content-Type (instead of application/vnd.wap.multipart.related or mixed) and follow by the text. | |||
| Forest Luo New member Username: Forest_luo Post Number: 29 Registered: 04-2004 |
Have you tried Nokia or other phone. There are some compatiable problems about MMS in different vendors. | |||
