Well, this implementations are nowadays confined to gw/smsc_http.c, so
it's quite simple to add a new one without bloating the rest of the
code.
Until someone comes with some a-la-apxs pluggable architecture (any
volunteers? ;) ), that's the way to do it. Not as clean as it could
be, but fair enough imho.
Regards,
--
Alejandro Guerrieri
[email protected]
On 25/05/2009, at 23:09, Milan P. Stanic wrote:
On Mon, 2009-05-25 at 17:28, Juan Nin wrote:
There are already several HTTP SMSC specific implementations on
Kannel, the ones that Hervé mentioned are some of them.
Kannel supports SMPP, EMI, UCP, AT, several HTTP and the others
protocols. I hope that the kannel will not become to bloated if we
tried to push every variant of HTTP specific implementation into it.
Of course you can do it directly without Kannel, but it's a good
approach to do it via Kannel, so that you always use it as your
gateway and not one method for some carriers and another one for
others, It's also nice to do it via Kannel cause it already
implements
stuff like it's internal queue, etc
--
Kind regards, Milan
