Hi guys,
I've been using Qpid for the past several months and I really like it. However,
I've mainly just been using it to pass messages between several Python
processes running on the same machine, so using Qpid is probably overkill. Then
I noticed Proton and got excited. Ideally I'm looking
ary 15, 2013 8:44 AM
To: proton@qpid.apache.org
Subject: Re: Is Proton a lightweight alternative to Qpid?
On Mon, Jan 14, 2013 at 11:14 AM, Eagy, Taylor wrote:
> Hi guys,
>
>
>
> I've been using Qpid for the past several months and I really like it.
> However, I've ma
sed on Proton-J) to their project recently.
-Ted
On 01/15/2013 12:37 PM, Eagy, Taylor wrote:
> Rafael,
>
>
>
> Thanks for responding. The only reason why I said it wouldn't be portable is
> because when I saw the CMake files I thought I'd have to build it to bind C
>
oss wrote:
> Taylor,
>
> You need the following files:
>
> proton.py (from proton-c/bindings/python)
> cproton.py (from $BUILD/bindings/python)
> _cproton.so(from $BUILD/bindings/python)
> libqpid-proton.so (from $BUILD)
>
> -
.send()
Thanks,
Taylor
From: Rafael Schloming [r...@alum.mit.edu]
Sent: Thursday, January 17, 2013 11:10 AM
To: proton@qpid.apache.org
Subject: Re: Subscribing to multiple queue names on the same host/port
On Thu, Jan 17, 2013 at 10:06 AM, Eagy, Taylor wrote:
> O
at I need to turn off to remove any references to the build directory? The
reason I need to do this is because when I copy it over to a clean install of
the same Linux version, it spits out that import error.
Thanks,
Taylor
From: Eagy, Taylor [te...@blackbirdtech
hey may act in unexpected ways.
You may need to set the environment variable LD_LIBRARY_PATH to your
local directory so the loader can find the library file if it's not in a
standard install location.
I hope this helps,
-Ted
On 01/22/2013 06:02 PM, Eagy, Taylor wrote:
> Ted,
>
>
