[
https://issues.apache.org/jira/browse/PROTON-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553808#comment-13553808
]
Ken Giusti commented on PROTON-199:
---
+1 for 2.4 - that's the oldest version of python th
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 mainly just been using it to pass messages between several
> Python processes running on the same machine, so using Qpid is probably
> ove
Hi.
I'm interested in testing Proton against the RabbitMQ AMQP 1.0 adapter.
But I'm struggling with the APIs I need to use to write even a simple
program. I'm using the Java version but from what I can see the C
version has the same APIs.
If I try to use the Messenger API then I don't see ho
On Tue, Jan 15, 2013 at 9:33 AM, Simon MacMullen wrote:
> Hi.
>
> I'm interested in testing Proton against the RabbitMQ AMQP 1.0 adapter.
> But I'm struggling with the APIs I need to use to write even a simple
> program. I'm using the Java version but from what I can see the C version
> has the s
On 15/01/13 15:29, Rafael Schloming wrote:
I'm guessing you need to set an address on the message. Messenger doesn't
expose direct control over connections or links. It will figure out what
connections/links to establish based on what address you specify on the
message (kind of like SMTP). You co
Ken Giusti created PROTON-200:
-
Summary: [Proton-c] Credit distribution by messenger is not
balanced across all links
Key: PROTON-200
URL: https://issues.apache.org/jira/browse/PROTON-200
Project: Qpid Pr
On Mon, Jan 14, 2013 at 2:48 PM, Darryl L. Pierce wrote:
> On Mon, Jan 14, 2013 at 02:35:08PM -0500, Rajith Attapattu wrote:
>> Rafi,
>>
>> We should create tags for the releases.
>> Unless I have missed (in which case I apologize), I don't see any for
>> 0.1 and 0.2 releases (I do see branches fo
The staging repo has been released, the RCs were copied over to dist last
night, and the download page was updated this morning. I've also created a
0.3 branch.
--Rafael
On Mon, Jan 14, 2013 at 4:31 PM, Darryl L. Pierce wrote:
> On Mon, Jan 14, 2013 at 02:14:26PM -0500, Rafael Schloming wrote:
>
Yes, the Python version works as I would expect, modulo:
* It strips the leading "/" from the target address
* On my machine, "localhost" resolves to ::1, and Proton appears not to
support IPv6.
But both of those can be worked around. Thank you!
Cheers, Simon
On 15/01/13 16:11, Rafael Schlom
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
functions from the engine to Python. However, if I can perform the p2p
messaging just using the proton.py then that would work. My s
Taylor,
Another possibility to look at is using ActiveMQ as your broker. They've
added an AMQP transport (based 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
be
Ted,
Proton is more lightweight and the systems that it runs on won't have Java
installed. While I would prefer a more Pythonic portable solution, as long as
Proton-c builds within 5MB, then it should work. However, I'm getting a bunch
of undefined reference messages from pythonPYTHON_wrap.c
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)
-Ted
On 01/15/2013 03:35 PM, Eagy, Taylor wrote:
Ted,
On Tue, Jan 15, 2013 at 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 functions from the engine to Python. However, if I can perform the
>
If you run cmake this way you can build the minimal code needed for just
the proton library and its python bindings:
cmake -DCMAKE_INSTALL_PREFIX=/usr -DBUILD_PYTHON=ON -DBUILD_PHP=OFF
-DBUILD_PERL=OFF -DBUILD_RUBY=OFF
A quick test on my system shows that a make install based on the above
build
15 matches
Mail list logo
