| The difference between client & gateway |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
can anyone tell me the implement differences of wsp,wtp between the client & gateway? | |||
| Bryce Norwood - NowSMS Support |
Well, let's take the basics ... A WTP client sends a WTP INVOKE, and gets back a WTP RESULT. I wouldn't expect that sequence to go back the other direction. Most clients would only have a connection to one gateway, whereas a gateway would manage connections to many clients. The concepts are certainly similar, but it's kind of like the differences between an HTTP client and an HTTP server or HTTP proxy server. | |||
| ooze |
thank u! Bryce | |||
| rajeshkannan Unregistered guest |
can any one tell the differnce between sms and mms ? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 989 Registered: 10-2002 |
In layman's terms, SMS is a text message ... MMS is a multimedia/picture message. SMS messages are limited to 160 characters (or 140 binary bytes or 70 Unicode characters) in the GSM environment. There is support for concatenation where larger messages can be split into multiple messages for sending, and then be reassembled by the receiving terminal. But generally speaking there aren't many terminals that support reassembly of more than 5 concatenated messages. So while there is some limited picture messaging and ring tone support in SMS (Nokia Smart Messaging and EMS being the primary implementations), the size limits are very small when you figure that 5 SMS messages can only hold 700 bytes of data (and because of concatentation headers, you usually lose 12 bytes per message ... meaning 640 bytes of actual data in 5 SMS messages). MMS was developed to allow richer multimedia content to be delivered in a manner similar to SMS. In today's environment, MMS is implemented using a combination of SMS and WAP technologies. Mobile devices are notified of a new MMS message being received by a special MMS notification message that is sent over SMS. That notification message contains a URL pointer to the content of the MMS message, and the recipient device opens a WAP (usually over GPRS) session to retrieve the MMS content. As the MMS content is transmitted over WAP, much larger message sizes are supported for MMS. (Low end MMS phones support at least 30K size for an MMS message.) -bn | |||
