| MMS-WAP-HTTP |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Murali Mohan.K |
Hi, I need clarification on the following: 1. How a notification is sent to an MMS Client running on HTTP ?? . Since notification comes as WAP-Push over SMS, the client will not be able to decode the WAP-Push PDU. 2. Assume that the MMS Client can decode the WAP-Push and WAP-MMS PDU but has got only HTTP for download, is it possible to download a WAP-encapsulated MMS using HTTP instead of WAPStack, since WAP-MMS PDU is just a content that can be fetched from the server. Awaiting in response... Thanx in advance.. | |||
| Bryce Norwood - NowSMS Support (Bryce) |
1. Then it not an MMS client (at least not one that is compatible with today's implementations ... it could still be considered an MMS client per the spec requirements). While an MMS client could certainly use HTTP to send/retrieve MMS clients (instead of doing it over a WAP stack), it must be capable of receiving the WAP Push PDU for the MMS notification. 2. Yes, this is possible. Just beware that if you are designing an MMS client for real world implementation, however, that many operators have firewalls around their MMSCs so that only the WAP gateway is allowed to connect to the MMSC. (This is why PDA MMS clients implement a WAP stack when they could just as well do HTTP direct.) -bn | |||
