On 13 February 2016 at 08:59, Garlapati Sreeram Kumar wrote:
> Hello All!
>
> Question on reactor framework expected behavior:
> - I am implementing an AmqpClient (for Azure EventHubs) and using
> reactor.connection(connxnHandler) to get a new out-bound connection and then
> creating sessions &
On 13 February 2016 at 00:28, Andrew Buckley wrote:
> I'm using the reactor with Proton-J and have noticed that there is a 2-4
> second delay between when I call send() on a particular link and when that
> transfer frame actually goes out. Is this expected behavior? If so, are there
> plans to
Cliff Jansen created PROTON-1132:
Summary: Timeout in valgrind test
Key: PROTON-1132
URL: https://issues.apache.org/jira/browse/PROTON-1132
Project: Qpid Proton
Issue Type: Bug
Comp
http://qpid.2158936.n2.nabble.com/VOTE-Release-RC-3-as-Qpid-Proton-0-12-0-td7638133.html
http://qpid.2158936.n2.nabble.com/VOTE-Release-RC-3-as-Qpid-Proton-0-12-0-td7638134.html
The vote passes with 9 in favor (7 binding) and none against.
Proton 0.12.0 is approved for release.
Justin
[
https://issues.apache.org/jira/browse/PROTON-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147367#comment-15147367
]
ASF subversion and git services commented on PROTON-1132:
-
Commit
[
https://issues.apache.org/jira/browse/PROTON-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen closed PROTON-1132.
Resolution: Fixed
> Timeout in valgrind test
>
>
> Key: PR
[
https://issues.apache.org/jira/browse/PROTON-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated PROTON-1063:
Fix Version/s: (was: 0.12.0)
0.13.0
> ruby: ruby reactor holds GVL in proces
[
https://issues.apache.org/jira/browse/PROTON-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway updated PROTON-1064:
Fix Version/s: (was: 0.12.0)
0.13.0
> ruby: add ConnectionEngine alterntive
[
https://issues.apache.org/jira/browse/PROTON-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway updated PROTON-1046:
Fix Version/s: (was: 0.12.0)
0.13.0
> C++ multi-threaded broker example
> --
[
https://issues.apache.org/jira/browse/PROTON-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway updated PROTON-1094:
Fix Version/s: (was: 0.12.0)
0.13.0
> c++: refactor and documentation of ty
Github user alanconway commented on the pull request:
https://github.com/apache/qpid-proton/pull/65#issuecomment-184307353
The problem is that the addresses used by proton are modelled on URLs, and
those characters are not safe in a URL path:
From RFC 1738 specification:
Github user gemmellr commented on the pull request:
https://github.com/apache/qpid-proton/pull/65#issuecomment-184320477
I hadn't got round to looking at this closely but was likely just going to
apply it if nothing obvious came up, and probably wouldnt have considered the
above.
Github user astitcher commented on the pull request:
https://github.com/apache/qpid-proton/pull/65#issuecomment-184349901
I think that @alanconway has a good point.
Looking at the C implementation of the url decoder it doesn't seem to
expand the % escapes for the path, but as
[
https://issues.apache.org/jira/browse/PROTON-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147716#comment-15147716
]
ASF subversion and git services commented on PROTON-629:
Commit 13
[
https://issues.apache.org/jira/browse/PROTON-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147715#comment-15147715
]
ASF subversion and git services commented on PROTON-1083:
-
Commit
[
https://issues.apache.org/jira/browse/PROTON-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher updated PROTON-629:
---
Labels: easyfix patch (was: build easyfix patch)
> Can't include proton-c header files in c-o
[
https://issues.apache.org/jira/browse/PROTON-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-629.
Resolution: Fixed
Fix Version/s: 0.13.0
> Can't include proton-c header files in c-on
Github user ssorj commented on the pull request:
https://github.com/apache/qpid-proton/pull/65#issuecomment-184352363
In previous discussion on APIs and bindings, we have said that we'd like to
use the language-native URL facilities if feasible.
---
If your project is set up for it,
[
https://issues.apache.org/jira/browse/PROTON-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147756#comment-15147756
]
ASF subversion and git services commented on PROTON-250:
Commit 87
[
https://issues.apache.org/jira/browse/PROTON-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147754#comment-15147754
]
ASF subversion and git services commented on PROTON-250:
Commit 05
[
https://issues.apache.org/jira/browse/PROTON-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147755#comment-15147755
]
ASF subversion and git services commented on PROTON-250:
Commit 52
[
https://issues.apache.org/jira/browse/PROTON-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147757#comment-15147757
]
ASF subversion and git services commented on PROTON-250:
Commit ca
Chuck Rolke created PROTON-1133:
---
Summary: Proton C includes port number in AMQP Open hostname
Key: PROTON-1133
URL: https://issues.apache.org/jira/browse/PROTON-1133
Project: Qpid Proton
Issue
[
https://issues.apache.org/jira/browse/PROTON-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147816#comment-15147816
]
ASF subversion and git services commented on PROTON-988:
Commit f7
[
https://issues.apache.org/jira/browse/PROTON-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-988.
Resolution: Fixed
Fix Version/s: 0.13.0
I've fixed the blatant issue here, but I've n
I've been doing some build tree maintenance in Proton and a couple of
issues have come up:
1. Is anyone using/have a reason to want to keep proton-dump? It's a
somewhat odd program that seems to have been a debugging tool left over
from the very earliest days of proton.
It uses the internals of t
[
https://issues.apache.org/jira/browse/PROTON-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147836#comment-15147836
]
ASF subversion and git services commented on PROTON-515:
Commit de
+1, +1.
I'm ok with both these changes.
Proton dump was handy on some occasions when new clients were sending bogus
frames that got confused by Wireshark. Normally Wireshark is fine but
proton-dump is a good authority. It was probably more useful in proton's
infancy and is unused today.
I use
- Original Message -
> From: "Andrew Stitcher"
> To: "proton" , "Qpid Developers"
>
> Sent: Monday, February 15, 2016 5:03:40 PM
> Subject: Dropping proton-dump; Moving to newer minimum CMake version
>
> I've been doing some build tree maintenance in Proton and a couple of
> issues ha
29 matches
Mail list logo