The best way you could do it would be by pooling your database constantly, and retrieving the message once is received. That is, let your application to guard the database against any received message... Optionally you could delete the message just after you got it, so that you'll be sure that your target table has only one message for every time you read from it.
On Thursday, September 27, 2012 6:22:22 PM UTC+2, emmy wrote: > > Good sir and thanks for sparing me little of your time. > i,m already communicating with the smsserver's database, what i mean > is this: when the server receiver any message it should pass it to my > application where it is processed and the reply text should be sent to the > smserver_out table for sending. i already have the Application ready and > the server working, all i need is to retrieve the TEXT and ORIGINATOR as > soon as the inboundMessage method gets them and the routine( retrieving, > processing and replying) should continue as long as the smserver is running. > > thanks in advance sir................ > -- You received this message because you are subscribed to the Google Groups "SMSLib Discussion Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msg/smslib/-/9_92CNOx-CgJ. For more options, visit https://groups.google.com/groups/opt_out.
