Re: Dropping proton-dump; Moving to newer minimum CMake version

- 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

[jira] [Commented] (PROTON-515) Port to OpenVMS

[ https://issues.apache.org/jira/browse/PROTON-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15147836#comment-15147836 ] ASF subversion and git services commented on PROTON-515: Commit

Dropping proton-dump; Moving to newer minimum CMake version

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

[jira] [Resolved] (PROTON-988) pn_messenger_set_flags does not support new SASL flag correctly

[ 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

[jira] [Commented] (PROTON-988) pn_messenger_set_flags does not support new SASL flag correctly

[ https://issues.apache.org/jira/browse/PROTON-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15147816#comment-15147816 ] ASF subversion and git services commented on PROTON-988: Commit

[jira] [Created] (PROTON-1133) Proton C includes port number in AMQP Open hostname

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

[jira] [Commented] (PROTON-250) Add -fvisibility option when building shared libraries

[ https://issues.apache.org/jira/browse/PROTON-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15147755#comment-15147755 ] ASF subversion and git services commented on PROTON-250: Commit

[jira] [Commented] (PROTON-250) Add -fvisibility option when building shared libraries

[ https://issues.apache.org/jira/browse/PROTON-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15147757#comment-15147757 ] ASF subversion and git services commented on PROTON-250: Commit

[jira] [Commented] (PROTON-250) Add -fvisibility option when building shared libraries

[ https://issues.apache.org/jira/browse/PROTON-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15147756#comment-15147756 ] ASF subversion and git services commented on PROTON-250: Commit

[jira] [Commented] (PROTON-250) Add -fvisibility option when building shared libraries

[ https://issues.apache.org/jira/browse/PROTON-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15147754#comment-15147754 ] ASF subversion and git services commented on PROTON-250: Commit

[GitHub] qpid-proton pull request: Schema parsing should not be so greedy

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,

[jira] [Resolved] (PROTON-629) Can't include proton-c header files in c-only applications in visual studio

[ 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

[jira] [Updated] (PROTON-629) Can't include proton-c header files in c-only applications in visual studio

[ 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

[jira] [Commented] (PROTON-1083) [C++] Simplify the messaging events

[ https://issues.apache.org/jira/browse/PROTON-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15147715#comment-15147715 ] ASF subversion and git services commented on PROTON-1083: - Commit

[jira] [Commented] (PROTON-629) Can't include proton-c header files in c-only applications in visual studio

[ https://issues.apache.org/jira/browse/PROTON-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15147716#comment-15147716 ] ASF subversion and git services commented on PROTON-629: Commit

[GitHub] qpid-proton pull request: Schema parsing should not be so greedy

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] qpid-proton pull request: Schema parsing should not be so greedy

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:

[jira] [Updated] (PROTON-1094) c++: refactor and documentation of type conversions

[ 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

[jira] [Updated] (PROTON-1046) C++ multi-threaded broker example

[ 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 >

[jira] [Updated] (PROTON-1064) ruby: add ConnectionEngine alterntive integration style

[ 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

[jira] [Updated] (PROTON-1063) ruby: ruby reactor holds GVL in process

[ 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

[jira] [Closed] (PROTON-1132) Timeout in valgrind test

[ 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:

[jira] [Commented] (PROTON-1132) Timeout in valgrind test

[ https://issues.apache.org/jira/browse/PROTON-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15147367#comment-15147367 ] ASF subversion and git services commented on PROTON-1132: - Commit

[RESULT][VOTE] Release RC 3 as Qpid Proton 0.12.0

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

Re: Proton-J Reactor sending delay

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,

Re: proton-j reactor socket error recovery

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 >