RE : [RFC] implementing XML-SMS calls using libxml2 functions

"LOESCH Jean-Jacques" <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <[email protected]>
Hi, I agree with Stipe, i think that, it's better to use libxml2 functions than developping our own parser.

Anyway, for the XML-SMS: 

XML encoding for SMS messages                             J.P.T. Koponen
Internet-Draft                                                 T. Ikonen
Expires: April 15, 2002                                       L. Ziegler
                                                          First Hop Ltd.
                                                        October 15, 2001
                     XML encoding for SMS messages
                      draft-koponen-sms-xml-02.txt

(their draft has expire yesterday)

Me, and my company, are very interested in participating in this effort.

Jean-Jacques LOESCH
Chief Architect
Volubill > 
Tel: +33 4 76 04 37 11
Mob: +33 6 18 41 03 80
Fax: +33 4 76 04 37 98
 
mailto:[email protected]
http://www.volubill.com


-----Message d'origine-----
De : Stipe Tolj [mailto:[email protected]] 
Envoyé : mardi 16 avril 2002 12:46
À : [email protected]
Objet : [RFC] implementing XML-SMS calls using libxml2 functions

Hi all,

I'd like to hear votes for rolling current cvs tree back, espacially
the parts Bruno added for the XML-SMS support using the
octstr_append() implementation. 

We should do this with libxml2 functions. At least I would like to
strip things out again as soon as I have finished the libxml2
implementation.

Comments and votes please.

BTW, I have asked the guys from First Hop Ltd. (located in Espoo, FI)
if they are interested in working with the Kannel Group in an XML-SMS
working group that may produce the internet draft standards. Who is
going to participate?

Stipe

[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.