[
https://issues.apache.org/jira/browse/PROTON-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14121184#comment-14121184
]
Bozo Dragojevic commented on PROTON-657:
Trunk builds on OSX fine. I like your fix
[
https://issues.apache.org/jira/browse/PROTON-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-657.
Resolution: Fixed
OSX: build proton with homebrew openssl
[
https://issues.apache.org/jira/browse/PROTON-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher updated PROTON-657:
---
Fix Version/s: 0.8
OSX: build proton with homebrew openssl
Gordon Sim created PROTON-659:
-
Summary: if protons internal buffer gets large, performance can
suffer
Key: PROTON-659
URL: https://issues.apache.org/jira/browse/PROTON-659
Project: Qpid Proton
On Wed, 2014-09-03 at 21:08 -0400, Michael Goulish wrote:
- Original Message -
On Wed, 2014-09-03 at 04:18 -0400, Michael Goulish wrote:
Fabulous.
OK, I put them in my git repo:
https://github.com/mick-goulish/proton_c_clients.git
And there, they are
On Thu, 2014-09-04 at 02:35 +0200, Leon Mlakar wrote:
On 04/09/14 01:34, Alan Conway wrote:
On Thu, 2014-09-04 at 00:38 +0200, Leon Mlakar wrote:
On 04/09/14 00:25, Alan Conway wrote:
On Wed, 2014-09-03 at 12:16 -0400, Michael Goulish wrote:
OK -- I just had a quick talk with Ted, and
[
https://issues.apache.org/jira/browse/PROTON-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher reassigned PROTON-610:
--
Assignee: Andrew Stitcher
proton-c: messenger doesn't honour an advertised remote
[
https://issues.apache.org/jira/browse/PROTON-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher reassigned PROTON-574:
--
Assignee: Andrew Stitcher
proton-c: Messenger doesn't indicate when connection is
Hi!
Just a headsup. This commit breaks pn_accept() for me, it fails all the
time. I'm not using selectors but drive the socket
with libdispatch (from xdispatch) with a custom driver.
If I revert this commit the trunk is useable. I'll dig deeper what is
going on, I was focusing on getting SSL
[
https://issues.apache.org/jira/browse/PROTON-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14121593#comment-14121593
]
Rafael H. Schloming commented on PROTON-654:
Here is the repo:
[
https://issues.apache.org/jira/browse/PROTON-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming updated PROTON-654:
---
Assignee: Justin Ross
the proton page has no git info on it
[
https://issues.apache.org/jira/browse/PROTON-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming updated PROTON-651:
---
Assignee: Darryl L. Pierce
Export the proton version numbers via the bindings.
[
https://issues.apache.org/jira/browse/PROTON-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14121672#comment-14121672
]
Rafael H. Schloming commented on PROTON-651:
I've done this for python, ruby,
Hi,
I am not sure what you are trying to do with xdispatch. If you are
using and external loop and managing your own IO, you can bypass the
low level Proton IO primitives and access the proton engine directly.
This is how Qpid uses Proton.
If you were using the driver.c mechanism, please take a
[
https://issues.apache.org/jira/browse/PROTON-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming resolved PROTON-651.
Resolution: Fixed
Export the proton version numbers via the bindings.
[
https://issues.apache.org/jira/browse/PROTON-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming reassigned PROTON-651:
--
Assignee: Rafael H. Schloming (was: Darryl L. Pierce)
Export the proton
[
https://issues.apache.org/jira/browse/PROTON-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming resolved PROTON-652.
Resolution: Fixed
Expose the version and build details for Proton in the Ruby
[
https://issues.apache.org/jira/browse/PROTON-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming reassigned PROTON-652:
--
Assignee: Rafael H. Schloming (was: Darryl L. Pierce)
Expose the version and
[
https://issues.apache.org/jira/browse/PROTON-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming reassigned PROTON-648:
--
Assignee: Rafael H. Schloming (was: Andrew Stitcher)
Memory leaks on aborted
[
https://issues.apache.org/jira/browse/PROTON-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14121718#comment-14121718
]
Rafael H. Schloming commented on PROTON-648:
I believe this has been fixed on
A little confirmation --
in my testing of proton engine send/receive clients
I just now tested the performance of those clients built against Proton
Release version, versus Proton RelWithDebInfo version.
I did indeed find that both versions were the same at running my tests,
after averaging
[
https://issues.apache.org/jira/browse/PROTON-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming resolved PROTON-642.
Resolution: Fixed
SASL Servers need to be able to optionally handle clients that
[
https://issues.apache.org/jira/browse/PROTON-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming resolved PROTON-640.
Resolution: Fixed
IO completion port Windows IO for Proton
[
https://issues.apache.org/jira/browse/PROTON-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14121791#comment-14121791
]
ASF subversion and git services commented on PROTON-610:
Commit
[
https://issues.apache.org/jira/browse/PROTON-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-610.
Resolution: Fixed
Fix Version/s: 0.8
Thanks [~dnwe] for this fix -
I've applied most
[
https://issues.apache.org/jira/browse/PROTON-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14121813#comment-14121813
]
Cliff Jansen commented on PROTON-640:
-
from https://reviews.apache.org/r/24159
This
Hi Bozo,
I closed the JIRA before I noticed your issue. Please feel free to reopen
it if your investigations turns up any problems with it.
--Rafael
On Thu, Sep 4, 2014 at 11:33 AM, Bozo Dragojevic bo...@digiverse.si wrote:
Hi!
Just a headsup. This commit breaks pn_accept() for me, it
I'm getting an error when trying to receive messages from within a browser. The
same code runs fine when run from the command line using node.
The error message is:
Module.MessengerError {name: MessengerError, message: listen: Not
supported, constructor: function, toString: function}
The
Hi Ernie,
Quick response as I'm just going to bed.
Subscribing is fine from a browser so if say you are connecting to a
broker you can happily do a receive with an address like say localhost
or whatever, but a browser can't really act as a server - you are
clearly trying to get your browser
Hi Proton Subscribers,
We are using proton qpid for some AMQP software architecture proof
of concept. The objective is
use proton as our standard AMQP message client to router, gateway and
interface with user domain
applications and AMQP brokers like qpid, rabitmq, zeromq, etc.
While
30 matches
Mail list logo
