<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Thu, Oct 24, 2013 at 10:04 AM, Ben Merrills <span dir="ltr"><<a href="mailto:b.merrills@mersontech.co.uk" target="_blank">b.merrills@mersontech.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-GB" link="#0563C1" vlink="#954F72">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">That makes sense!
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">At the end of the day, I should only be getting information I can do something about, by default. And yes, I agree that it makes
sense to incorporate some options for the filtering too.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Ben<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif""> <a href="mailto:asterisk-app-dev-bounces@lists.digium.com" target="_blank">asterisk-app-dev-bounces@lists.digium.com</a> [mailto:<a href="mailto:asterisk-app-dev-bounces@lists.digium.com" target="_blank">asterisk-app-dev-bounces@lists.digium.com</a>]
<b>On Behalf Of </b>Kinsey Moore<br>
<b>Sent:</b> 23 October 2013 22:06<br>
<b>To:</b> Asterisk Application Development discussion<br>
<b>Subject:</b> [asterisk-app-dev] ARI Global Data Accessibility Changes<u></u><u></u></span></p><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Hello App Developers,<br>
We have been thinking about what information is exposed via the ARI requests for lists of channels (GET /ari/channels) and bridges (GET /ari/bridges). Currently, these requests return all information about any channel or bridge in the system.<br>
<br>
As an example, imagine you have channels SIP/Alice and SIP/Bob in the Stasis() application being bridged by ARI-created bridge Foo. In the same system, you also have channels SIP/Charlie and SIP/David being bridged by Dial()-created bridge DialBridge. When
you GET /ari/channels, you will receive:<br>
[<br>
{ "name": "SIP/Alice", ... },<br>
{ "name": "SIP/Bob", ... },<br>
{ "name": "SIP/Charlie", ... },<br>
{ "name": "SIP/David", ... }<br>
]<br>
<br>
When you GET /ari/bridges, you will receive:<br>
[<br>
{ "id": "Foo", ... },<u></u><u></u></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"> { "id": "DialBridge", ... }<br>
]<br>
<br>
This situation is non-ideal since channels SIP/Charlie and SIP/David and bridge DialBridge can not be acted upon via ARI. We propose limiting these queries to channels and bridges which ARI can affect. In this case, the /ari/channels query would return:<br>
[<br>
{ "name": "SIP/Alice", ... },<br>
{ "name": "SIP/Bob", ... }<br>
]<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">The /ari/bridges query would return:<br>
[<br>
{ "id": "Foo", ... }<br>
]<br>
<br>
The rework would also include an optional filter parameter for ARI user or Stasis application to increase the available granularity.<u></u><u></u></p>
</div>
<p class="MsoNormal"><br>
Kinsey Moore<br>
Digium, Inc. | Software Developer<br>
445 Jan Davis Drive NW - Huntsville, AL 35806 - US <u></u><u></u></p>
</div>
</div></div></div>
</div>
<br>_______________________________________________<br>
asterisk-app-dev mailing list<br>
<a href="mailto:asterisk-app-dev@lists.digium.com">asterisk-app-dev@lists.digium.com</a><br>
<a href="http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev" target="_blank">http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev</a></blockquote><div><br></div><div><br></div><div><br></div><div>
+1 - I'd still want to be able to access information about the whole system though - whether this is done with extra headers, as having filtering type stuff via params just doesn't feel right </div></div><br></div>
</div>