[asterisk-dev] ARI, reinventing the wheel?

[Tilghman Lesher]

On Mon, Oct 21, 2013 at 1:28 PM, Paul Albrecht <palbrecht at glccom.com> wrote:
>
> On Oct 21, 2013, at 11:09 AM, Jared Smith <jaredsmith at jaredsmith.net> wrote:
> > 3) The program in step one then controls the business logic of the call.  It
> > might, for example, make an HTTP call over the REST interface to the
> > /ari/channels/{channelId}/answer, to tell Asterisk to answer that particular
> > channel.  The program might use REST APIs to play sounds, start call
> > recording, create bridges, etc.  As these things happen, events continue to
> > get generated on the Stasis bus, and the program reads those events from the
> > websocket connection.
>
> How's this *NOT*" reinventing the AMI wheel? All of this could be
> accomplished with AMI with the exception of flowing the protocol over a web
> socket. If that's a requirement, why not fix asterisk to do that and benefit
> everyone?

What about the fact that using the same API as a ton of other external
projects (a RESTful interface), and this consequently makes
integrating Asterisk more available to a wider audience of developers?

If it's not your cup of tea, don't use it.  Nobody is forcing you to
partake, Paul.

-Tilghman