Re: [FYI] HTTP request queueing of sms-services

Stipe Tolj <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Organization Wapme Systems AG
Message-ID <[email protected]>
Mauricio Ramos wrote:
> 
> 1) What will happen if Kannel has been gracefuly shut down and still there
> are get-urls queued?  Kannel would recover the queue from store-file and
> keep requesting the remaining times?

Hmm, same problem as with queued outbound SMS messages. 

No, smsbox is not accessing the store-file in any way, hence if you
shutdown smsbox with an non-empty HTTP request queue, the requests are
lost. Which is of course not perfect, but at least better then
dropping the requests directly after HTTP request failure.

> 2) Shouldn't this mechanism be in sms-service group configuration rather
> than smsbox group?  So http queueing would be configured on a
> per-application basis.

Hmmm, yeah, at least the 'queueing on/off' switch is of global scope,
hence appropriate to the smsbox group. 

What you intend is to turn queueing then again on/off for certain
sms-service groups, which is reasonable, but not a problem if
currently not implemented. I guess this will go to the TODO list
section in the STATUS file. You may contribute a patch for this if you
want it in there?!

> 3) Now, not in regards of the get-urls but dlr-urls, is there a way this
> queueing mechanism be available for DLR http requests?  I realized that
> dlr-url requests are retried just one time and than they are left in
> store-file.  When I restart Kannel it just retry them more two times and so
> far every time I restart Kannel.  Isn't it wrong?

No, the DLR URL HTTP requests are performed within the scope of
bearerbox (in the single smsc modules to be exact), not smsbox. But
this may be abstracted for various DLR supporting modules within the
scope of bearerbox and a queueing may be implemented -> TODO.
Patches?!

> 4) Why MySQL hasn't been used to store get-urls like dlr-urls?

MySQL hay have been used almost for storing everything, even the
store-file hay have been implemented with a MySQL. But we don't want
tooo much dependecies from other libraries or sub-systems.

Maybe we can abstract the HTTP request queueing of both boxes to 2
threads, each in one box, with a combined http-store-file?! What do
the others think about this issue?

Stipe

[email protected]
-------------------------------------------------------------------
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: [email protected]
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.