I deeply agree on using meta-data for most TLV's, specially the user-
defined ones, but the particular case with receipted_message_id is
that it's being used a more and more by carriers (at least on my
experience) and would require a lot more work and decoding at the
application level just to get the SMSC id.
I personally think that having the SMSC message id as part of the
regular data being carried forth and back it's a "good thing", but
that's of course just my opinion.
Having means to capture any parameter into meta-data would be a
wonderful feature, though I'd allow receipted_message_id have it's own
field. In fact, I'd study means to allow this to get into the logs as
well (I'm sure many people would welcome having the original message
id on their logs).
Regards,
Alejandro Guerrieri
El 20/11/2008, a las 06:44 p.m., Alexander Malysh escribió:
Stipe Tolj schrieb:
Arne K. Haaje schrieb:
We have been running this patch for a bit, and it works great for
capturing the message_id. Thanks Alejandro! :)
thanks Arne, I'll count this as a +1 vote then.
Any other objections out there? Otherwise I'll go to commit the
changes, or
Alejandro can do it on it's own ;)
I would like to see this implemented with meta-data instead of
adding yet another field...
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
-------------------------------------------------------------------
