Github user dnwe commented on the pull request:
https://github.com/apache/qpid-proton/pull/27#issuecomment-99380746
@dcristoloveanu I'd be happy to merge these changes in for you as it is
certainly better for the library not to segfault if a malloc fails.
However, I do wonder
GitHub user dnwe opened a pull request:
https://github.com/apache/qpid-proton/pull/28
NO-JIRA: improvements to export.sh
+ allow specific tag to be specified as cmdline arg
+ confirm the tag exists before proceeding
+ use the version.txt from that tag as the tar prefix
Github user rhs commented on the pull request:
https://github.com/apache/qpid-proton/pull/26#issuecomment-99432258
Looks good to me. On the struct initialization stuff, it might be worth
seeing if we can make gcc turn those into errors if it causes problems on other
compilers.
---
The Java test runs have apparently been failing since the last few
commits went in for the Go bits.
https://builds.apache.org/job/Qpid-proton-j/
Robbie
On 6 May 2015 at 00:48, Alan Conway acon...@redhat.com wrote:
First serious stab at a concurrent Go API for proton with working examples
Github user asfgit closed the pull request at:
https://github.com/apache/qpid-proton/pull/28
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/qpid-proton/pull/28
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
[
https://issues.apache.org/jira/browse/PROTON-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14530373#comment-14530373
]
ASF subversion and git services commented on PROTON-827:
Commit
When we were implementing the MQ Light broker, we wanted to be able to support
sharing of subscriptions across a group of clients - in particular for the
worker offload scenario. At the time we were unable to find guidance in the
specification or extensions thereof, so we went ahead with
Github user dnwe commented on the pull request:
https://github.com/apache/qpid-proton/pull/28#issuecomment-99431533
Removed by 81c2110
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
-Robbie Gemmell robbie.gemm...@gmail.com wrote: -
The Java test runs have apparently been failing since the last few
commits went in for the Go bits.
https://builds.apache.org/job/Qpid-proton-j/
I spotted this as it was also causing a `make install` to fail on the proton-c
jenkins.
Github user gemmellr commented on the pull request:
https://github.com/apache/qpid-proton/pull/28#issuecomment-99423851
A little more info:most of the changes are to ensure the dir within the tar
matches the version, in case the tag name does not (e.g a proposed final RC
being voted
Bump this up.
I'm essentially in the same boat. The olso.messaging library in Openstack has
introduced a feature called 'consumer pools' which is essentially the same
pattern: a set of subscribers to a topic can belong to a pool. Each distinct
pool of subscribers get a copy of the message
On 05/06/2015 10:05 AM, Ken Giusti wrote:
Bump this up.
I'm essentially in the same boat. The olso.messaging library in Openstack has
introduced a feature called 'consumer pools' which is essentially the same
pattern: a set of subscribers to a topic can belong to a pool. Each distinct
Github user rhs commented on a diff in the pull request:
https://github.com/apache/qpid-proton/pull/28#discussion_r29751867
--- Diff: bin/export.sh ---
@@ -54,15 +65,18 @@ WORKDIR=$(mktemp -d)
##
(
cd ${SRC}
-TAG=$(git describe --tags --always)
Github user rhs commented on the pull request:
https://github.com/apache/qpid-proton/pull/28#issuecomment-99428883
Fixing the prefix in the tarball makes sense to me, however some of the
other changes do not. The release process is supposed to proceed from a signed
tag, which means
Github user asfgit closed the pull request at:
https://github.com/apache/qpid-proton/pull/26
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Adrian Preston created PROTON-881:
-
Summary: Proton-j reactor implementation
Key: PROTON-881
URL: https://issues.apache.org/jira/browse/PROTON-881
Project: Qpid Proton
Issue Type:
Github user rhs commented on the pull request:
https://github.com/apache/qpid-proton/pull/29#issuecomment-99635551
Given my recent rant about new development on master, let's try pulling
this in on a branch first. I've create the proton-j-reactor branch. If you can
resubmit against
Github user prestona closed the pull request at:
https://github.com/apache/qpid-proton/pull/29
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user prestona commented on the pull request:
https://github.com/apache/qpid-proton/pull/29#issuecomment-99640540
Closing. Will submit again against proton-j-reactor
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
[
https://issues.apache.org/jira/browse/PROTON-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14531717#comment-14531717
]
Adrian Preston commented on PROTON-877:
---
The patch works for me in that I can now
Hallo,
I am trying to integrate protom messenger with a regular select-based event
loop.
Regrettably there's not much documentation about reading and sendingn messages
in passive mode using selectros. Can you give a quick look to the pseudo-code,
describing message input in my event loop
[
https://issues.apache.org/jira/browse/PROTON-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-868.
Resolution: Fixed
Fix Version/s: 0.10
Make Pipelined ANONYMOUS authentication work
[
https://issues.apache.org/jira/browse/PROTON-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14531460#comment-14531460
]
ASF subversion and git services commented on PROTON-334:
Commit
On Wed, 2015-05-06 at 22:22 +0100, Gordon Sim wrote:
[ 70%] Building C object
proton-c/bindings/javascript/CMakeFiles/qpid-proton-bitcode.dir/__/__/src/sasl/sasl.c.o
/home/gordon/projects/proton-git/proton-c/src/sasl/sasl.c:224:9: error:
implicit declaration of function 'strncasecmp' is
On some recent traces to an ActiveMQ 5.12 broker I observed that the broker
signals some info in the open frame:
capability:ANONYMOUS-RELAY,
property:{topic-prefix:topic://, queue-prefix:queue://}
Having written clients that try to go to ActiveMQ brokers and to Qpid brokers,
getting the
Gordon Sim created PROTON-880:
-
Summary: make Array iterable
Key: PROTON-880
URL: https://issues.apache.org/jira/browse/PROTON-880
Project: Qpid Proton
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/PROTON-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved PROTON-880.
---
Resolution: Fixed
make Array iterable
---
Key: PROTON-880
[
https://issues.apache.org/jira/browse/PROTON-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14531492#comment-14531492
]
ASF subversion and git services commented on PROTON-879:
Commit
- Original Message -
From: Ted Ross tr...@redhat.com
To: proton@qpid.apache.org
Sent: Wednesday, May 6, 2015 10:25:32 AM
Subject: Re: AMQP 1.0 and Shared Subscriptions
On 05/06/2015 10:05 AM, Ken Giusti wrote:
Bump this up.
I'm essentially in the same boat. The
[
https://issues.apache.org/jira/browse/PROTON-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14531410#comment-14531410
]
ASF subversion and git services commented on PROTON-827:
Commit
[
https://issues.apache.org/jira/browse/PROTON-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14531411#comment-14531411
]
ASF subversion and git services commented on PROTON-827:
Commit
[
https://issues.apache.org/jira/browse/PROTON-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14531461#comment-14531461
]
ASF subversion and git services commented on PROTON-880:
Commit
[
https://issues.apache.org/jira/browse/PROTON-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-879.
Resolution: Fixed
null initial response makes cyrus challenge when it probably shouldn't
[
https://issues.apache.org/jira/browse/PROTON-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14531400#comment-14531400
]
ASF subversion and git services commented on PROTON-868:
Commit
[
https://issues.apache.org/jira/browse/PROTON-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher updated PROTON-867:
---
Description: Currently PLAIN is never offered by Proton acting as a server
because the SASL
On 05/06/2015 10:28 PM, Andrew Stitcher wrote:
On Wed, 2015-05-06 at 22:22 +0100, Gordon Sim wrote:
[ 70%] Building C object
proton-c/bindings/javascript/CMakeFiles/qpid-proton-bitcode.dir/__/__/src/sasl/sasl.c.o
/home/gordon/projects/proton-git/proton-c/src/sasl/sasl.c:224:9: error:
implicit
On Wed, May 6, 2015 at 10:59 AM, Alan Conway acon...@redhat.com wrote:
On Thu, 2015-04-30 at 21:51 -0400, Rafael Schloming wrote:
What sort of work/connections are you talking about here? Are you talking
about processing AMQP messages in a thread pool or are you talking about
writing some
[
https://issues.apache.org/jira/browse/PROTON-860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14531007#comment-14531007
]
Gordon Sim commented on PROTON-860:
---
Patch for review:
The recent landing of the Go changes make me think that we should be more
explicit about our development process with respect to new language
bindings (or possibly in general). There are two problems I would like to
address.
First, a bunch of code just landed on trunk without prior
[
https://issues.apache.org/jira/browse/PROTON-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14531789#comment-14531789
]
ASF GitHub Bot commented on PROTON-877:
---
GitHub user prestona opened a pull request:
GitHub user prestona opened a pull request:
https://github.com/apache/qpid-proton/pull/30
Reactor
This is an initial implementation of a proton-j version of the reactor. It
comes with samples, unit tests and interoperation tests. It should be good
enough to kick the tyres but
Oh dear. I think I might have confused ASF GitHub Bot. This is a PR relating
to PROTON-881, in which I (foolishly) mentioned ROTON-877...
Regards
- Adrian
Adrian Preston, IBM WebSphere MQ Development - Hursley - MQ Light
-ASF GitHub Bot (JIRA) j...@apache.org wrote: -
To:
On Wed, 2015-05-06 at 12:32 +0100, Dominic Evans wrote:
-Robbie Gemmell robbie.gemm...@gmail.com wrote: -
The Java test runs have apparently been failing since the last few
commits went in for the Go bits.
https://builds.apache.org/job/Qpid-proton-j/
I spotted this as it was
On Thu, 2015-04-30 at 21:51 -0400, Rafael Schloming wrote:
What sort of work/connections are you talking about here? Are you talking
about processing AMQP messages in a thread pool or are you talking about
writing some sort of multithreaded I/O handler?
I'm talking about running multiple
On Wed, 2015-05-06 at 11:35 +0100, Robbie Gemmell wrote:
The Java test runs have apparently been failing since the last few
commits went in for the Go bits.
https://builds.apache.org/job/Qpid-proton-j/
Robbie
On 6 May 2015 at 00:48, Alan Conway acon...@redhat.com wrote:
First serious
On 6 May 2015 at 15:54, Gordon Sim g...@redhat.com wrote:
Moving to the user list as this is a more general topic.
On 05/06/2015 12:41 PM, Dominic Evans wrote:
When we were implementing the MQ Light broker, we wanted to be able
to support sharing of subscriptions across a group of clients -
47 matches
Mail list logo
