| Use of base64 in "X-Wap-Application-Id: 4" ??? |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through March 23, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Bliss Unregistered guest |
hi, I am wondering if it is of any use to base64-encode the part of the notification (MMS) that specifies Content-Location, Transaction ID, etc. In fact it is only (and always) text, so base64-encode it only results in a bigger POST to do. My problem comes when putting together MMS-Relays and PPGs... but I think it should never be encoded, as there is no advantage and there is some size increase. Thanks for your opinions!! :-) Bliss | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1137 Registered: 10-2002 |
Bliss, How are you submitting this?? I can't think of anywhere that you would use Base64 encoding on those fields. You might use Base64 encoding when submitting an MMS message via MM7 (or MM4/SMTP e-mail interface) ... but the MMSC should be expected to decode that before sending it out over the air. But what has me confused is that I can't see where the headers that you mention would ever be Base64 encoded, even in MM7 or MM4. So please explain more detail! -bn | |||
