[asterisk-app-dev] How do third party moduledevelopersexposetheir resources via asterisk ARI?

[Matthew Jordan]

On Fri, Oct 18, 2013 at 9:27 AM, Paul Albrecht <palbrecht at glccom.com> wrote:

>
> On Oct 17, 2013, at 1:58 PM, "David M. Lee" <dlee at digium.com> wrote:
>
> >
> > On Oct 17, 2013, at 1:23 PM, Paul Albrecht <palbrecht at glccom.com> wrote:
> >
>
>
<snip>


> >
> > I've put my wish-list to enable external ARI modules on my (newly
> created) ARI future work page[1].
> >
> >> That said, I would expect an interface to register/unregister resource.
> Also, changing a resource shouldn't require recompiling asterisk.
> >
> > It doesn't require recompiling Asterisk; the C code is modular. But the
> code generator needs some love in order to make this work well. (Hence my
> short list for ARI future work).
> >
> > As far as registering a resource with ARI, the main function is
> ast_ari_add_handler()[2]. That call, and the code to build the
> stasis_rest_handlers tree that gets passed into it, resides in the
> generated res/res_ari_{resource}.c file.
> >
>
> Suppose this will work, but why not implement resources the usual way
> asterisk does this sort of thing? That is, create an object via a
> registration interface and then call the methods on the object when they're
> needed. For resources, it would be something like register the uri and
> callbacks for the rest methods and then invoke the methods via the object
> when then accessed.
>
> > [1]: https://wiki.asterisk.org/wiki/x/mQeUAQ
> > [2]:
> http://doxygen.asterisk.org/trunk/d4/d59/ari_8h.html#d960fe775504c2df60bcb7f7f9beb5b2
> >
> > --
>


Paul:

This is the second time you've been asked not to cross-post. Developers who
are working on ARI and can answer your questions are on all of the mailing
lists. Please do not cross post across the mailing lists - replying on one
of the mailing lists is sufficient.

Thanks,

Matt

-- 
Matthew Jordan
Digium, Inc. | Engineering Manager
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: http://digium.com & http://asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-app-dev/attachments/20131018/710079f0/attachment.html>