Because langs already have encoders/parsers for JSON :)<div><br></div><div>Would be good to be able to set the format by the format you login with; if this ever happened that is. </div><div><br></div><div>So you'd login with a JSON string and therefore subsequent replies would come through as JSON</div>
<div><br></div><div>In terms of there being "a few" AMI commands, surely they all follow a data structure and the data gets encoded into \n\n before being sent out? And therefore changes would be in the encoder and decoder part of the AMI?</div>
<div><br></div><div>Dan Jenkins</div><div><br></div><div><br></div><div><br></div><div><br></div><div class="gmail_extra"><br clear="all"><font face="arial, helvetica, sans-serif" color="#333333">-- <br>Dan Jenkins - Senior Web Developer<br>
email: <a href="mailto:dan.jenkins@holidayextras.com" target="_blank">dan.jenkins@holidayextras.com</a><br>twitter: <a href="http://twitter.com/dan_jenkins" target="_blank">dan_jenkins</a><br>linkedin: <a href="http://www.linkedin.com/in/jenkinsdaniel" target="_blank">jenkinsdaniel</a><br>
skype: <a>d-jenkins</a></font><div><font face="arial, helvetica, sans-serif" color="#333333">blog: <a href="http://www.dan-jenkins.co.uk/" target="_blank">www.dan-jenkins.co.uk</a></font></div><div><font face="arial, helvetica, sans-serif" color="#333333"><a href="http://about.me" target="_blank">about.me</a>: <a href="http://about.me/dan_jenkins" target="_blank">about.me/dan_jenkins</a></font></div>
<br>
<br><br><div class="gmail_quote">On 9 November 2012 09:28, Saúl Ibarra Corretgé <span dir="ltr"><<a href="mailto:saghul@gmail.com" target="_blank">saghul@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
+1 for Olle's suggestion. On to the format...<div class="im"><br>
<br>
Nir Simionovich wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Ok, that’s a +1 by me as well. But, if we go that route, I think we<br>
should be able to format the output of that<br>
action. It would be very useful. Honestly, while on the subject, and I<br>
do admit that what I’m about to say will<br>
be totally out there – it would be really nice if the input to AMI can<br>
be a single JSON array, instead of doing the<br>
ever annoying \n\n in manager – no?<br>
<br>
</blockquote>
<br></div>
Why? You'll get text so you'll need to JSON-decode it anyway, so what's wrong about \n\n ?<br>
<br>
If we go that route someone may want XML as well so then we should have a way to tell AMI to give you the result of a given query in text, JSON or XML format. Or maybe set the format for a given AMI session/connection. Doesn't sound like a bad idea, but there are "a few" AMI commands out there ;-)<br>
<br>
<br>
Regards,<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Saúl Ibarra Corretgé<br>
<a href="http://saghul.net/blog" target="_blank">http://saghul.net/blog</a> | <a href="http://about.me/saghul" target="_blank">http://about.me/saghul</a></font></span><div class="HOEnZb"><div class="h5"><br>
<br>
--<br>
______________________________<u></u>______________________________<u></u>_________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/<u></u>mailman/listinfo/asterisk-dev</a><br>
</div></div></blockquote></div><br></div>