Do you mean, queueing for the HTTP interface? Place your code inside the HTTP interface - you probably need to keep the notifications locally and call the HTTP URLs.
On Jun 27, 12:35 am, Sri <[email protected]> wrote: > Which portion of the code is the best place to modify if I am > implementing my own queuing. > > On Jun 19, 2:27 pm, Thanasis <[email protected]> wrote: > > > > > Agree with Aryo. If the DB interface covers you needs, look no > > further. > > > About your second question, the HTTP notification for in/out are NOT > > queued. > > > On Jun 19, 5:23 am, Aryo Sanjaya <[email protected]> wrote: > > > > On Fri, Jun 19, 2009 at 03:28, Sri <[email protected]> wrote: > > > > > What are the other ways > > > > of sending messages from outside SMS Server apart from this? One > > > > method I am aware of is inserting a record into the smssrv_out table. > > > > Is that really efficient? > > > > I think the best way to send message is by database interface. You can > > > easily check the queue, status, remove and many operations rather than > > > using > > > other interface. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SMSLib User Group" 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 -~----------~----~----~----~------~----~------~--~---
