If we have one thread why not to use some time-expired flags?<неи<неи<неиSay,
after sms was submitted, set "mute_submitting_till" to (now + 1.0/throughput),
where now = current time in usec<неи<неиThen if kannel wakes up, it do incoming
data processing, and if it wakes up before (mute_submitting_till < now) ==
true, he don't send anything and do gwthread_sleep(now -
mute_submitting_till)<неи<неи<неиStas.<неи<неи-----Original
Message-----<неиFrom: Vincent CHAVANIS [mailto:[EMAIL PROTECTED] <неиSent:
Sunday, May 13, 2007 11:51 PM<неиTo: Stanislaw Senotrusov<неиCc:
[email protected]<неиSubject: Re: bug in throughput?<неи<неиYes this is true. We
have an old issue here.<неиWe are trying to find a global solution for this but
this is not so trivial.<неиYou can use/adapt a patch (for EMI/UCP Smsc) i
posted few month ago to the <неиML<неиIf i remember well, Stuart Beck has
already adapted it for SMPP.<неиBut we get a new issue after using this patch,
the Throughput will be <неиrespected<неиbut you will limit the incoming stream
because we have only one thread that <неиdo RX and
TX<неи<неиVincent<неи<неи----- Original Message ----- <неиFrom: "Stanislaw
Senotrusov" <[EMAIL PROTECTED]><неиTo: <[email protected]><неиSent: Sunday, May
13, 2007 10:52 AM<неиSubject: bug in throughput?<неи<неи<неи> Hello.<неи><неи>
My SMPP connection is configured with throughput = 1<неи><неи> Looking at logs
I see what kannel trying to do submit_sm more than 1 per <неи>
second.<неи><неи> I have a 1 message per second limit, and carrier SMSC
responds to my<неи> high volume message flow with SMSC returned error code
0x00000008<неи> (System Error) in response to submit_sm<неи><неи> As I noticed,
throughput handled through gwthread_sleep() function<неи> which is unblocked on
incoming data in socket.<неи><неи> So, kannel do submit_sm, and then trying to
sleeps for 1 second, but<неи> that sleep is breaks by incoming data from
SMSC.<неи><неи> Am I right or I can't get something?<неи><неи> -- <неи>
Stanislaw Senotrusov<неи><неи> <неи<неи
