Re: req_feat patch

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rene Kluwen wrote:

> ???
>  
> So which exactly is the _standard_ http? As far as I know, a
> sms-over-http RFC doesn't exist.
> Every provider implements their own protocol.
> To which http variant do you want clickatell to move?
>  
> Anyhow... we discussed this before, back when the Clickatell API was
> admited to Kannel CVS.
> I don't feel like having the same discussion over again.
>  
> I don't mind if this patch is not in CVS. It will just mean that the
> Clickatell http driver is partly broken.

Not quite true, I have seen this one some years ago:

https://datatracker.ietf.org/public/idindex.cgi?command=id_detail&id=6181

It's a RFC draft in IETF (internet engeneering task force), AFAIR, it was a
simplified XML dialect over HTTP trnasport.

But not sure if it ever reached final state.

I "think" Hillel itends to have a "generic" HTTP API, and "addopt" the specific
SMSC provider details via config directives.

@Hillel: is this your intention? Did I understand it right?

Now, from my perspective this is VERY TRICKY. Since configuration directives
have only a limiting way in defining "logic" at runtime itself. Of course they
do, but it would be a vast of config directives needed to make the "differences"
of the various types logic to work.

Stipe

- -------------------------------------------------------------------
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany

tolj.org system architecture      Kannel Software Foundation (KSF)
http://www.tolj.org/              http://www.kannel.org/

mailto:st_{at}_tolj.org           mailto:stolj_{at}_kannel.org
- -------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGRfl69ez0oeKvYs0RAmq/AKC4bUKOijwS2TZbvkCt40nGih6SjgCgo6F1
vSutHYGliu1JrX9lLT7fw6U=
=jOk5
-----END PGP SIGNATURE-----