Re: [FYI] Post-XML

Stipe Tolj <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Organization Wapme Systems AG
Message-ID <[email protected]>
Bruno David Simões Rodrigues wrote:
> 
> As I don't yet have simple functions to parse xml, I've finished
> (almost) the xml post code.
> 
> There's some differences for latest
> http://www.ietf.org/internet-drafts/draft-koponen-sms-xml-03.txt
> IETF draft, like it just define a <statusrequest> and we have
> dlr-mask and dlr-url, so I've adjusted and set
> <statusrequest>
>         <dlr-mask>x</dlr-mask>
>         <dlr-url>http://....</dlr-url>
> </statusrequest>
> 
> and I've taked liberally the <from> and <to> (smsc directives) tags to
> have:
> kannel->appl: from = smsc-id, to=service-name
> appl->kannel: from = authentication, to=smsc-id
> 
> Please compile documentation with --enable-docs --enable-drafts or check
> at http://litux.org/~bruno/userguide.{html|rtf|pdf} and give me
> suggestions, critics, flames, anything.
> 
> I'll need this (or something alike) for the end of the week.....
> 
> On sendsms-user, it supports multiple destinations, altough I've yet not
> tested how many destinations we could have
> (BTW: do we have any string limit in octstr ? internally, multiple
> destinations is a string with numbers separated by space)

Ok, Bruno does the XML-Post routines and I do the XML-RPC routines,
which is not the same. The IETF draft you refer is ment for SMS
requests via XML only. XML-RPC is a general approach for remote
procedure calls via HTTP transport.

So we're going to have 2 URIs refering to the different XML processing
routines.

Stipe

[email protected]
-------------------------------------------------------------------
Wapme Systems AG

Münsterstr. 248
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: [email protected]
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are
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.