[jdev] WSDL with HTTP binding/REST interface/WSDL with XMPP bindings for XMPP server

Wed Mar 4 02:42:14 CST 2009

> -----Original Message-----
> From: jdev-bounces at jabber.org [mailto:jdev-bounces at jabber.org] On
> Behalf Of Antoine Toulme
> Sent: 04 March 2009 10:10 AM
> To: jdev at jabber.org
> Subject: Re: [jdev] WSDL with HTTP binding/REST interface/WSDL with
> XMPP bindings for XMPP server
> 
> 
> 
> 
> Peter Saint-Andre-2 wrote:
> >
> > On 2/2/09 9:12 PM, Antoine Toulme wrote:
> >> Hey everyone, I would like to communicate with a XMPP server through
> a
> >> WSDL.
> >
> > How and why?
> >

I don't see any reason why you couldn't write a binding/transport like that. I guess it would work very similarly to BOSH. I could see a few benefits - but you will need to decide if the effort it worth it: there are a whack of XMPP libraries out there and you shouldn't need to go anywhere near WSDL endpoints. This would not be the easy solution I assume you are looking for. Keep away from it.

@PSA, this could actually be quite a neat XEP. Although I don't know how much benefit we could possibly derive from it, apart from being able to do the following:

<soap:body>
 <stream:stream xmls:stream="..." xmlns="jabber:client">
  <iq id="foo"> <!-- Not valid but it works on most servers anyway -->
   <query xmlns="jabber:iq:auth">
    <username>spammer</username>
    <password>spamisfun</password>
   </query>
  </iq>

  <message to="victim at capulet.org" from="spammer at seveneleven.com">
   <body>SPAM! SPAM! SPAM! Get your spam for only $2 at your closest Seven11 store today!</body>
  </message>
 </stream:stream>
</soap:body>

But XMPP over WSDL is definitely a good example of why XMPP is so superior compared to other networks.

> > The idea was to interact with Google Talk. So I hoped there was a
> WSDL to
> > send messages to Gtalk.

Again, I could almost guarantee there is an XMPP library in the language you are using. <http://xmpp.org/software/libraries.shtml>

> >
> >> As far as I understand, it is possible to interact with a XMPP
> server by
> >> sending XML messages over XMPP respecting the XMPP schemas, right ?
> >
> > As defined in RFC 3920, yes (that is for the TCP binding).

And you could use these schemas in the WSDL document, but it would be a rather large one. If you read some other stuff on the list, there are portability issues with the schemas, because some libraries don't support namespaces 100% correctly (I, by the way, am going to disregard those libraries; XML is XML full stop).

> >> Any other binding would work as long as it is supported by any other
> XMPP
> >> server: over HTTP, with or without the SOAP envelope, etc.
> >
> > The HTTP binding is defined here:
> >
> > http://xmpp.org/extensions/xep-0124.html

That is what BOSH is by the way. If you are behind a firewall or NAT that is blocking port 5222/3 you could always resort to Jabber80.org. They run a jabber server behind port 80 (this is a normal TCP binding, however).

> >
> > Ok, thanks!
> >
> > Peter
> >
> > --
> > Peter Saint-Andre
> > https://stpeter.im/
> >
> >
> >
> > _______________________________________________
> > JDev mailing list
> > Forum: http://www.jabberforum.org/forumdisplay.php?f=20
> > Info: http://mail.jabber.org/mailman/listinfo/jdev
> > Unsubscribe: JDev-unsubscribe at jabber.org
> > _______________________________________________
> >
> >
> 
> --
> View this message in context: http://www.nabble.com/WSDL-with-HTTP-
> binding-REST-interface-WSDL-with-XMPP-bindings-for-XMPP-server-
> tp21799264p22325391.html
> Sent from the Jabber JDEV mailing list archive at Nabble.com.
> 
> _______________________________________________
> JDev mailing list
> Forum: http://www.jabberforum.org/forumdisplay.php?f=20
> Info: http://mail.jabber.org/mailman/listinfo/jdev
> Unsubscribe: JDev-unsubscribe at jabber.org
> _______________________________________________