[asterisk-dev] Unified Asterisk Interface

[Tilghman Lesher]

On Tuesday 11 December 2007 08:02:37 David Roden wrote:
> On Monday 10 December 2007 20:17:58 Jim Capp wrote:
> > This makes sense, but it is a little scary.  I like the separation of
> > AGI and AMI from Asterisk.
>
> And that separation makes sense. What does not make sense (IMHO) is that
> there are two APIs that each allow you to access a certain subset of
> Asterisk's features only and no API that can be used to utilize every
> feature Asterisk has to offer. (Just to make sure: The kind of API I'm
> talking about allows access to Asterisk's features without access to the
> source code.)

Um, one is a synchronous interface that is a child of the Asterisk process
itself (AGI) and the other is an asynchronous interface that can be used
from anywhere (AMI).  I don't see how you could possibly combine the two
and get a coherent interface.

> > It allows us to build things without encumbering the server itself.
>
> Right. Currently I have to add three different AGI calls to an Asterisk
> dialplan for my application to work. This is something I would like to get
> rid of, or cut down at least to the required minimum--which would be a
> single line.

Well, if you're addicted to AGI, you're going to love 1.6, since we've joined
the boundary between live and dead mode and allowed an AGI to make the
transition.

-- 
Tilghman