| MM7 single-attachment: multipart or not? |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through August 08, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Antonio Unregistered guest |
Hi, everybody.. The questions are: 1) when sending an MM with a single attachment, must the attachment of the SOAP message be "multipart/...(related or mixed, whether the single attachment is a SMIL or not)" or with no multipart-container at all? Apache SOAP API don't use any multipart-container with a single attachment... 2) is it 3GPP-compliant to send a SOAP message with a single attachment as a SMIL? I know, it seems crazy, but is it formally right? Thanks | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2500 Registered: 10-2002 |
If you are only sending a SMIL, does this mean that you have placed your text of the mesasge into the SMIL? That is a bit unusual. To be honest, I'm not sure if that is legal. At least I don't think that any text would be parsed out of the SMIL file itself without a "src" reference. But if you were sending a "text" file, or just an "image", with no SMIL, then yes, I believe it is legal for the attachment of the SOAP message to be just "text/plain" or "image/gif". It is always possible that some implementations might have a problem with it, but technically it would seem consistent with the 3GPP MMS specs. The 3GPP specs only state that multipart/related must be the content type for any MM7 requests that contain a SOAP attachment. It only says that the MIME type of this SOAP attachment "should have the appropriate content type(s) to identify the payload". In practical implementations, that type is generally multipart/related or multipart/mixed. But there is nothing in the specifications that says that it must be. | |||
