| WAP2.0 optional gw |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| ralphdt |
Hi Did I read in WAP2.0 that the WAPGW element becomes optional. WirelessTCP/HTTP replace the WAP stack? Will this impact MMSC implementation? Or just message encoding? I suspect a direct connection can be made to the MMSC and the MMS message content returned directly rather than via the WAPGW proxy. Daniel | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Daniel, Yes, in WAP 2.0, the WAP stack is optional. I doubt we'll see much of this (except in PDA clients) until 3G. Basically, with GPRS today, I've seen a lot of "dirty" connections in WAP gateway logs, where I think the WAP protocol is better for overcoming transmission problems. When it does change, I believe operators will prefer using HTTP proxies that implement Wireless TCP/HTTP to having clients connect to content servers directly. The interface to the MMSC doesn't change in either event, as an MMSC shouldn't be tied to a WAP stack. What will change in the MMSC world over time, is that eventually I believe we'll see IP-based notifications, and even IP-based polling for messages. -bn | |||
