On Oct 24, 2013, at 4:18 AM, Daniel Jenkins <dan.jenkins88 at gmail.com> wrote:
> +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
I've been giving this some thought. Here's my proposal:
The container list operations (GET /ari/bridges, GET /ari/channels),
when no parameters are given, will only return the objects that can be
acted upon via ARI.
However, a specific list of objects can be requested by passing in an
id list parameter (GET /ari/channels?channelIds=1234,5678,1357,9753).
These objects will be returned if they exist, regardles of whether ARI
can act upon them.
Similarly, single object requests (GET /ari/channels/{channelId}) will
always return that specific object if it exists.
Thoughts? Objections?
--
David M. Lee
Digium, Inc. | Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: www.digium.com & www.asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-app-dev/attachments/20131025/a4c50c58/attachment.html>
