RE: SOAP
"Rene Kluwen" <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Message-ID | <[email protected]> |
>From what I understand is that a simple http post request with content-type: text/xml and a SOAPAction: header conforms to the SOAP specifications... What am I overseeing in this matter? See: http://www.w3.org/TR/SOAP/. Rene Kluwen Chimit -----Original Message----- From: [email protected] [mailto:[email protected]]On Behalf Of Stipe Tolj Sent: donderdag 12 februari 2004 1:06 To: Rene Kluwen Cc: [email protected]; Oded Arbel Subject: Re: SOAP Rene Kluwen wrote: > > I am currently doing some SMSC/Soap thingies in C (so I may do what is needed here), my question is the following: > > What makes "SOAP" differ from a proprietary XML schema over HTTP. > Is there an "official" SOAP/XML DTD or schema for sending SMS messages? SOAP is actually the way the XML framework defines a RPC way of allowing to pass information entities arround. Yes, in some sense there is MMAP v1.0 which is a SOAP/XML based schema of doing SMS and multimedia transmission. Rene, you definetly should check the gSOAP project for this. Stipe mailto:[email protected] ------------------------------------------------------------------- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf, NRW, Germany phone: +49.211.74845.0 fax: +49.211.74845.299 mailto:[email protected] http://www.wapme-systems.de/ ------------------------------------------------------------------- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.2.2 (Cygwin) mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2 nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H g2HyLAEKQIp30Q== =aYCI -----END PGP PUBLIC KEY BLOCK-----