I think the best way is when inbound notification is invoked, read all unread message and save them in Database/Table.
Then use own queue inbound process from the database to process, then reply back. On 9/24/08, Thanasis <[EMAIL PROTECTED]> wrote: > > Hi, > > Let me explain: > First of all, all messages are read and the modem is released. > Then, the callback method's process() is called one by one. > > If you think that your process() method will take more than some > seconds, it would be advisable if you decoupled your processing logic > from the callback method, i.e. use the callback method to queue up > messages and use some other thread to process them and reply. > > > On Sep 23, 7:50 pm, waywardsoul <[EMAIL PROTECTED]> wrote: >> Hi, >> >> Am using SmsLib for an application that will be receiving quite a >> number of sms all the time. I need to know how the callback methods >> (Notifications) are called. Am wondering whether SmsLib calls the >> process() method for every message received Asynchronously or each >> notification will be allowed to complete before the next is processed. >> The problem is that I need to send a reply message inside the >> process() method and I think I may not be able to do that if SmsLib >> calls process() for the next received sms. I will only be using one >> gateway. >> >> regards >> >> Alex. > > > -- -- nokideen, ym : nokideen sms : 08385956664 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SMSLib Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SMSLib?hl=en -~----------~----~----~----~------~----~------~--~---
