| APIs for processing MO messages |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through May 12, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Pawel Zdziarski Unregistered guest |
As far as I know your gateway does not have Java APIs. In some other thread I saw you suggest your HTTP APIs instead. Fine, but is that efficient enough for processing incoming (i.e. MO) messages? Our apps would then have to pool the gateway periodically, right? Do you have experience with customers who have done that? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2256 Registered: 10-2002 |
Hi Pawel, When our gateway receives an SMS message, it calls an HTTP URL that you specify in the configuration. So there is no polling involved. A separate thread in NowSMS processes the HTTP callbacks, so other gateway activity continues while the callbacks are being processed. This approach is reasonably efficient. Unless your script requires a lot of processing, our experience has shown that messages can be processed at a rate of 3 to 4 messages per second. If you need to process inbound messages at a faster rate, beginning with the v5.50 release of NowSMS (currently in beta, see http://www.nowsms.com/newsletter), it is possible to allocate additional threads to the receive SMS processing. To enable multithreaded processing of these commands, edit SMSGW.INI, and under the [SMSGW] section header, add 2WaySMSThreadCount=xx, where xx is a value greater than 1. In practice, the overhead of allocating additional threads for this processing is relatively low, as the threads spend most of their time waiting for a message to process or waiting for an HTTP response from the callback that is issued. -bn | |||
