[Foundation] Jabber-RPC payload council question

[Adam Theo]

> 
> jer asked a good question on the JEP voting for Jabber-RPC
> this month. As I only have read-only access to the list ;-)
> I was wondering how to answer - but David Waite did the
> honours:
> 
> http://mailman.jabber.org/pipermail/council/2001-September/000129.html
> 
> Thanks David.
> 
> For those interested / curious, the original question was
> valid, as we could have had something like this:
> 
> <iq type='set' to='responder at company-a.com/jrpc-server' id='1'>
>   <methodCall xmlns='jabber:iq:rpc'>
>     <methodName>examples.getStateName</methodName>
>     <params>
>       <param>
>         <value><i4>6</i4></value>
>       </param>
>     </params>
>   </methodCall>
> </iq>

i just had an idea. sorry i didn't think of this while the development
was going on:

what about create a new root tag? after all, for RPC stuff, it obviously
isn't a 'message' (talk), and it really isn't an 'iq' (query). it's a
command. so i'd suggest:

<rpc type="xml-rpc|soap|...">
  <methodCall>
  ...
</rpc>

or 

<command type="xml-rpc|soap|...">
  <methodCall>
  ...
</command>