[asterisk-app-dev] Adapting the Node ARI Module to work with the Proxy Message Protocol

Phil Mickelson phil at cbasoftware.com
Mon Feb 8 07:26:22 CST 2016


Thanks for the clarification.  I wish I had the time to learn more!

PhilM
On Feb 8, 2016 8:23 AM, "Ben Merrills" <b.merrills at mersontech.co.uk> wrote:

> PhilM,
>
>
>
> The service bus used is more dependent on the proxy and not the client
> (although both need to support of course).
>
>
>
> In both the Go and .NET proxies, RabbitMQ is supported, the Go proxy also
> supports NATS.IO.
>
>
>
> Ben
>
>
>
>
>
> *From:* asterisk-app-dev-bounces at lists.digium.com [mailto:
> asterisk-app-dev-bounces at lists.digium.com] *On Behalf Of *Phil Mickelson
> *Sent:* 08 February 2016 13:08
> *To:* Asterisk Application Development discussion <
> asterisk-app-dev at lists.digium.com>
> *Subject:* Re: [asterisk-app-dev] Adapting the Node ARI Module to work
> with the Proxy Message Protocol
>
>
>
> I read your issue and would love to get away from the 1:1 problem.  I've
> been using the node-ari-client for some time now successfully and find that
> to be the only major issue.  I do like having Swagger to do testing so I
> assume if it's changed there will be other methods?  Also, I use ZeroMQ
> instead of RabbitMQ but I assume that both would work?
>
>
>
> Thank you for bringing this up and making it work!
>
>
>
> PhilM
>
>
>
> On Mon, Feb 8, 2016 at 5:24 AM, Dan Jenkins <dan.jenkins88 at gmail.com>
> wrote:
>
> Hi Everyone,
>
>
>
> I just wanted to bring attention to this issue I wrote on the
> node-ari-client's repo -
> https://github.com/asterisk/node-ari-client/issues/37
>
>
>
> I'm just about to start some work with the ARI and want to be able to use
> the Proxy messaging protocol with the Go Proxy and the Node module.
> However, as the proxy isn't a drop in replacement it'll mean doing some
> work to the module to get things going.
>
>
>
> I'm making the wider community aware of the issue here and asking for any
> feedback. For the time being I think I'm going to have to fork the module,
> get the work done, and then look at merging it back in which is a shame but
> I think theres too much to change (especially in how the module's internals
> are created using swagger) to do it in a way that makes it easy to merge
> back in happily once I'm done.
>
>
>
> Dan
>
>
> _______________________________________________
> asterisk-app-dev mailing list
> asterisk-app-dev at lists.digium.com
> http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev
>
>
> ------------------------------
>
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2016.0.7357 / Virus Database: 4522/11559 - Release Date: 02/05/16
>
> _______________________________________________
> asterisk-app-dev mailing list
> asterisk-app-dev at lists.digium.com
> http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-app-dev/attachments/20160208/5b4ebfa4/attachment.html>


More information about the asterisk-app-dev mailing list