On Thu, 14 Apr 2005, Anand Gupta wrote:
May i ask if you are a kannel code hacker as well, since you know so much on kannel ? I see the message_id feature is required by other users as well however no one seems to have gotten to it. I was kind of interested to explore the possibility of getting it done and then perhaps submit it to kannel development team for review. This way who so ever wants the feature will benefit from this.
I am not, yet. I may need to become one to get this implemented, though there are many in the devel list that are more talented and better versed in the inner workings than I.
There is a bit of a developer dispute on how to pass the message_id. Some feel that implementing the ts variable with the message_id will make the kannel code impure, since the ts variable is really for a timestamp, not an arbitrary message id. Evaluating the DLR URL at the time of storing the DLR for the message to replace an escape code with the message id has been poo-pooed as well as a hack. Adding a new variable that would not replace but be in addition to the ts variable has been suggested but sneered at since the bearerbox knows the message ID but the smsbox is responsible for calling the DLR url.
The great thing about open source is that you can fuss with it yourself to make it work. The bad thing about open source is that when the core developers see a way around a problem (i.e. the DLR report from your SMSC give you the message ID without code modifications, so why modify the code that works just fine for both SMSC and direct phone connections), they don't regard the problem as highly. And usually the core developers are the heaviest users of their own code, and they haven't found a need to store the message ID (it seems, I'm presuming a lot here), so it hasn't been a priority.
I wonder if cash thrown at the developers would maybe get a few arbitrary features put into kannel, done "the right way"...
Beckman --------------------------------------------------------------------------- Peter Beckman Internet Guy [EMAIL PROTECTED] http://www.purplecow.com/ ---------------------------------------------------------------------------
