[jdev] In-Band RPC and SOAP discovery

[Peter Saint-Andre]

On 05/22/2008 7:25 AM, Jonathan Dickinson wrote:
> Hey all,
> 
> What are the options here?
> 
> One potentially elegant solution would be (for XMPP-RPC):
> 
> C:
> <iq type='get'
>     from='requester at company-b.com/jrpc-client'
>     to='responder at company-a.com/jrpc-server'
>     id='disco1'>
>   <query xmlns='http://jabber.org/protocol/disco#info'/>
> </iq>
> 
> S:
> <iq type='result'
>     to='requester at company-b.com/jrpc-client'
>     from='responder at company-a.com/jrpc-server'
>     id='disco1'>
>   <query xmlns='http://jabber.org/protocol/disco#info'>
>     <identity category='automation' type='rpc'/>
>     <feature var='jabber:iq:rpc'/>
>     <identity category='automation' type='jabber:iq:rpc' />
>     <feature var='http://www.mycompany.org/xml-rpc/example.ConvertCurrency.php' />

What exactly does that identify? Is that a *feature* or a *service*?

If it's a service, it's better to identify it via disco#items or even
XEP-0215 as Maciek notes, because the service is external to the XMPP
network.

<snip/>

> <wsdl:definitions name='SomeService'
>   targetNamespace='http://www.myserver.org/soap/someservice'
>   xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/' />

Or:

<definitions

<wsdl:definitions
      xmlns='http://schemas.xmlsoap.org/wsdl/'
      name='SomeService'
      targetNamespace='http://www.myserver.org/soap/someservice'/>

Six of one, half a dozen of the other. :)

I'm not a huge WSDL fan, but what you've described will work, I think.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7338 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://www.jabber.org/jdev/attachments/20080522/574f1eb2/attachment-0002.bin>