Hi Stipe,
it's pretty simple why we need 2 ints. We need to track 2 values: a)
time of last resend, in order to not to send too oft (delayed); b) how
much retries we did.
If you know how to awoid or better to say how track 2 values within one
int I would like to hear.
Thanks,
Alex
Stipe
Alexander Malysh wrote:
Hi Stipe,
it's pretty simple why we need 2 ints. We need to track 2 values: a)
time of last resend, in order to not to send too oft (delayed); b) how
much retries we did.
If you know how to awoid or better to say how track 2 values within one
int I would like to
hmm, time_t as bit operations... Good luck ;)
Thanks,
Alex
Stipe Tolj wrote:
Alexander Malysh wrote:
Hi Stipe,
it's pretty simple why we need 2 ints. We need to track 2 values: a)
time of last resend, in order to not to send too oft (delayed); b) how
much retries we did.
If you know how
Alexander Malysh wrote:
Index: gwlib/cfg.def
===
RCS file: /home/cvs/gateway/gwlib/cfg.def,v
retrieving revision 1.112
diff -a -u -p -r1.112 cfg.def
--- gwlib/cfg.def21 Sep 2005 02:01:22 -1.112
+++ gwlib/cfg.def26
Stipe Tolj wrote:
+1 on the logic, I assume you did regression test this Alex, did you?
I'm -1 on the new config directive naming, and I'd like to change it to:
sms-resend-freq
sms-resend-retry
Reasons:
'sms-resend-freq' follows naming convention as introduced to prior
config
Hi,
as no objections were here, commited to cvs.
Thanks,
Alex
Alexander Malysh wrote:
Hi all,
please find attached patch that adds configurable max retries and resend
frequency for the temporarily failed messages to the core (means works
with all SMSC modules). Patch also includes changes
Hi all,
please find attached patch that adds configurable max retries and resend
frequency for the temporarily failed messages to the core (means works
with all SMSC modules). Patch also includes changes to user guide for
how to use it.
Please give me feedback...
Thanks,
Alex
Index:
