Re: Http request & kannel

Angel Fradejas wrote:
> 
> My opinion is that if smsbox can't fetch content from a web server, it must
> queue that request, and try again later, with a specified delay between
> requests, instead of the current "couldn't fetch content" reply.
> 
> Any other opinions about this?

yep, that *may* be a logical valid solution. But it arrises a lot of
problems, some are technical and others are logical.

For the technical side, think of queue size, timeouts etc. For the
logical side, I think we break semantics if we queue requests and
process them later. If a user requests a URL to a sms-service at
timestamp A and the responsible HTTP server is not available at that
time, the request gets queued and at timestamp B kannel succeeds to
re-send the request, the HTTP server processes the requests and
answers. But at timestamp B the request *may* have not the same
locgical and semantical meaning as in timestamp A and hence we break
semantics here.

Stipe

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

Münsterstr. 248
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