[PATCH] Support for MO parameters on 'generic' HTTP SMSC

Alejandro Guerrieri alejandro.guerrieri at gmail.com
Sun Sep 2 15:41:20 CEST 2007


Hillel,

My patch only allows to rename all incoming (MO) parameters for the
'generic' HTTP SMSC only. Clickatell and other HTTP SMSC's are not
directly affected (they implement their own parameter mapping).

I can extend my patch to accept extra parameters, but I'm not sure how
to map those new parameters to "real things".

I'll check the clickatell code and see how far it is from be
abstracted into the generic http smsc. As I've said, not all http
smsc's can be implemented with this patch, since some of them has
unique features that cannot be covered by a generic interface with
renamed parameters and return strings.

Regards,

On 9/2/07, Hillel <hillel at ecommunicate.biz> wrote:
> Hi Alejandro,
>
> Please explain will your patch allow Kannel users to set their own MO
> parameters as well?
> If it does not do this, then are you prepared to extend your generic patch
> to allow the Kannel user to set their own parameters for MO and MT?
>
> If you will allow this, then Rene's patch (req_feat patch Rene Kluwen Wed,
> 09 May 2007 06:26:20 -0700)
> that was suggested for a new Clickatell parameter would not be needed and
> your patch could become the default standard for HTTP MO and MT that will
> work for Clickatell and others.
>
> This should then have a great chance to be accepted as it will cover future
> additions by Clickatell and others as Kannel users can then add their own
> parameters.
>
> Rgds
>
>


-- 
Alejandro Guerrieri
Magicom
http://www.magicom-bcn.net/
LinkedIn: http://www.linkedin.com/in/aguerrieri



More information about the devel mailing list