Hi Daniel,<div><br></div><div>Yes, the RPC API does support nested struct, but at first glance the XMLRPC doesn't. The sercmd test you did will work so long as you use named pipe transport. If you try and do a ul.dump using XMLRPC you will get an error on the nested structure fmt "{". I will have a look at it today and let you know.</div>
<div><br></div><div>Cheers</div><div>Jason<br><br><div class="gmail_quote">On Mon, May 14, 2012 at 11:20 PM, Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
xmrpc is not going to be deprecated, it is actually the newer one.<br>
<br>
But it is implementation from scratch, no external xmlrpc being
used. So far it was implemented as much as it was needed. However,
nested structures in replies should be supported. What is exactly
the error you get? If there is an issue, it has to be fixed.<br>
<br>
I just tested 'sercmd ul.dump' and worked fine, returning:<br>
<br>
{<br>
Domain: location<br>
Size: 512<br>
AoRs: {<br>
AoR: 401<br>
HashID: 3325474<br>
Contacts: {<br>
Contact: {<br>
Address: <a>sip:401@192.168.178.22:1024;line=1uxhrhwy</a><br>
Expires: 3541<br>
Q: 0.000000<br>
Call-ID: 3c267033369e-d3i5csinl2h7<br>
CSeq: 6300<br>
User-Agent: snom370/8.4.35<br>
Received: [not set]<br>
Path: [not set]<br>
State: CS_NEW<br>
Flags: 0<br>
CFlags: 0<br>
Socket: udp:<a href="http://192.168.178.21:5060" target="_blank">192.168.178.21:5060</a><br>
Methods: 6111<br>
Ruid: uloc-4fb17657-71d-1<br>
Instance:
<urn:uuid:3d1a0962-4751-426f-8492-0004132672E3><br>
Reg-Id: 1<br>
}<br>
}<br>
}<br>
Stats: {<br>
Records: 1<br>
Max-Slots: 1<br>
}<br>
}<br>
<br>
It has lot of inner structures.<br>
<br>
Cheers,<br>
Daniel<div><div class="h5"><br>
<br>
<br>
<div>On 5/14/12 5:14 PM, Jason Penton wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">Hi All,
<div><br>
</div>
<div>I have just been testing xmlrpc on some of the IMS module RPC
functions and got some errors using nested structures. viz "{".
Having a quick look through the xmlrpc code show that it doesn't
support nested structures in the reply.</div>
<div><br>
</div>
<div>I am quite happy to fix this but am surprised that nobody has
mentioned this before as I see there are a few modules that use
nested replies. Does this maybe mean that XMLRPC is going to be
deprecated (not a usual module)? </div>
<div><br>
</div>
<div><br>
</div>
<div>Cheers</div>
<div>Jason</div>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
sr-dev mailing list
<a href="mailto:sr-dev@lists.sip-router.org" target="_blank">sr-dev@lists.sip-router.org</a>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><span class="HOEnZb"><font color="#888888">
</font></span></pre><span class="HOEnZb"><font color="#888888">
</font></span></blockquote><span class="HOEnZb"><font color="#888888">
<br>
<pre cols="72">--
Daniel-Constantin Mierla - <a href="http://www.asipto.com" target="_blank">http://www.asipto.com</a>
<a href="http://twitter.com/#!/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/miconda</a></pre>
<br>
<br>
</font></span></div>
</blockquote></div><br></div>