Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (nike.apache.org: domain of
 prvs=0541433f7f=rhs@alum.mit.edu designates 18.7.68.18 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <55259285.5080407@redhat.com>
References: <55259285.5080407@redhat.com>
Date: Thu, 9 Apr 2015 00:02:45 -0400
Message-ID: 
 <CACL1BnCC8M3_9cdscZcUwiGYPxoDHFwjotG9v2fpcr+xM7UBuA@mail.gmail.com>
Subject: Re: node.js api poc
From: Rafael Schloming <rhs@alum.mit.edu>
To: "users@qpid.apache.org" <users@qpid.apache.org>
Content-Type: multipart/alternative; boundary=047d7b86d8e064f8cf051342b8cf

--047d7b86d8e064f8cf051342b8cf
Content-Type: text/plain; charset=UTF-8

Hi Gordon,

Can you explain a bit more about the issues you ran into wrapping the C
reactor? I'm building a system that needs to communicate between python and
javascript, so I'm glad to see more work on the javascript bindings, but I
will need to be able to use the same C handlers from both python and
javascript, in particular handlers that create new connections. Does that
still work with what you've done, or is there a way to get that to work?

--Rafael


On Wed, Apr 8, 2015 at 4:41 PM, Gordon Sim <gsim@redhat.com> wrote:

> Following on from recent work on the python examples, I've been exploring
> what the equivalent might be for node.js. For anyone interested in
> commenting or collaborating around this, or even just having a look at it,
> I've posted my current progress including examples at
> https://reviews.apache.org/r/32737
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>

--047d7b86d8e064f8cf051342b8cf--