I believe that this parameter should be set optimally at msec and not
sec to handle throttling rates such as 100 messages per sec., because
for each second we sleep after receiving 0x58 we lose the opportunity to
transfer these 100 messages, and transmission rate is reduced significantly.
> Looks good. As C goes it's fine. I just hope it is useful enough to
justify
> the configuration expansion.
>
> +1
>
> BR,
> Nikos
> ----- Original Message -----
> From: "Michael Zervakis" <[email protected]>
> To: <[email protected]>
> Sent: Wednesday, February 04, 2009 7:51 PM
> Subject: Please have a look at this patch adding option to configure
> SMPPthrottling sleep time
>
>
> > Hi,
> >
> > I noticed that SMPP transmitter will sleep for 15 seconds when
> > receiving a 0x58 (ESME_RTHROTTLED) response declaring that ESME has
> > exceeded allowed message limits per second. This setting is hardcoded
> > and I think 15 sec is a long time to wait, so I created this patch to
> > allow user to configure this parameter as following:
> > group = smsc
> > smsc = smpp
> > .....
> > throttling-sleep-time = 5
> >
> > Please have a look at this patch (C is not one of my core
competencies).
> >
> >
> >
