[asterisk-app-dev] ARI Global Data Accessibility Changes

[Corey Edwards]

On Fri, Oct 25, 2013 at 1:53 PM, David M. Lee <dlee at digium.com> wrote:
>
> On Oct 25, 2013, at 1:48 PM, Paul Belanger <paul.belanger at polybeacon.com> wrote:
>
>> So, in a more general term, we are talking about creating some sort of
>> filtering / query system for a bulk get. But rather then just
>> channelId, why not expose every parameter. So, if I want to see all
>> the up channels, I just pass state=up or specific channel types
>> name=SIP.  Personally, I think it gets complicated fast, and not sure
>> that's what the issue you are trying to solve is.
>
> Well, I do see a difference between retrieving information by id
> (in which you know that at most one object has that id) and filtering
> (where any number of objects may match the filter). However, over
> time, I can see us adding any number of query filters to our GET
> operations that return lists.
>
> I don't think that means we have to add all of them right now; just
> the ones we have use cases for.

One filter type that comes immediately to mind is Stasis application
name. If I'm building app_foo, then I'll might only want to see channels
or bridges from app_foo, and none other.

Corey