candidate commits for 0.9.1

Hi folks, Running git-cherry against 0.9 and master to compare their history since divergence results in the following output. Lines starting with '-' already have equivalent commits in 0.9 from the RC stages, lines starting with '+' do not. I am going to begin going through these and cherry

[jira] [Commented] (PROTON-853) [proton-j] the transport emitted a new link attach for a link in the process of being detached

[ https://issues.apache.org/jira/browse/PROTON-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14510759#comment-14510759 ] Robbie Gemmell commented on PROTON-853: --- The changes in this JIRA allow for rcv =

[jira] [Updated] (PROTON-853) [proton-j] the transport emitted a new attach frame for a link in the process of being closed

[ https://issues.apache.org/jira/browse/PROTON-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-853: -- Summary: [proton-j] the transport emitted a new attach frame for a link in the process of being

Re: Error handling in the proton-c reactor (and how it might relate to a Java port)

Hi Adrian, See inline for answers... On Thu, Apr 23, 2015 at 12:17 PM, Adrian Preston prest...@uk.ibm.com wrote: Hello all, While porting the proton-c reactor to Java, I've found a few error paths that I wasn't sure how best to handle. I have some ideas (see below), but if this stuff is

[GitHub] qpid-proton pull request: NO-JIRA: README improvements

GitHub user dnwe opened a pull request: https://github.com/apache/qpid-proton/pull/22 NO-JIRA: README improvements * remove out-of-date product information from the README and include the more current information from the website * add a new INSTALL file to contain the

[GitHub] qpid-proton pull request: NO-JIRA: README improvements

Github user rhs commented on the pull request: https://github.com/apache/qpid-proton/pull/22#issuecomment-95922186 +1 As a general note I think it's good to try to test changes to install/readme type stuff on people who aren't already intimately familiar with proton and all

[GitHub] qpid-proton pull request: NO-JIRA: README improvements

Github user asfgit closed the pull request at: https://github.com/apache/qpid-proton/pull/22 --- 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] qpid-proton pull request: NO-JIRA: README improvements

Github user dnwe commented on the pull request: https://github.com/apache/qpid-proton/pull/22#issuecomment-95931032 I've sent these off to be further reviewed by a few people round here to see if I can determine further improvements., Have merged them in as-is for now as I believe

Re: [GitHub] qpid-proton pull request: NO-JIRA: README improvements

Make install tries to install README instead of README.md. On Fri, Apr 24, 2015 at 9:21 AM, dnwe g...@git.apache.org wrote: Github user dnwe commented on the pull request: https://github.com/apache/qpid-proton/pull/22#issuecomment-95931032 I've sent these off to be further

[jira] [Created] (PROTON-864) don't overload top bit of channel numbers

michael goulish created PROTON-864: -- Summary: don't overload top bit of channel numbers Key: PROTON-864 URL: https://issues.apache.org/jira/browse/PROTON-864 Project: Qpid Proton Issue

[jira] [Created] (PROTON-865) C++ reactor client binding

Cliff Jansen created PROTON-865: --- Summary: C++ reactor client binding Key: PROTON-865 URL: https://issues.apache.org/jira/browse/PROTON-865 Project: Qpid Proton Issue Type: New Feature

[jira] [Commented] (PROTON-853) [proton-j] the transport emitted a new attach frame for a link in the process of being closed

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

[jira] [Commented] (PROTON-850) inconsistent state when reusing link name

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

[jira] [Commented] (PROTON-154) proton-j: link attach, detach, attach sequence on single session does not result in a new link for the 2nd attach

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

[jira] [Commented] (PROTON-853) [proton-j] the transport emitted a new attach frame for a link in the process of being closed

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

[jira] [Commented] (PROTON-344) Need Ruby version of msgr-send/msgr-recv tools

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

[jira] [Commented] (PROTON-862) Proton using Cyrus SASL library is problematic because the library has global state

[ https://issues.apache.org/jira/browse/PROTON-862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14511864#comment-14511864 ] Rafael H. Schloming commented on PROTON-862: It strikes me that we could

[jira] [Created] (PROTON-868) Make Pipelined ANONYMOUS authentication work with fallback SASL implementation

Andrew Stitcher created PROTON-868: -- Summary: Make Pipelined ANONYMOUS authentication work with fallback SASL implementation Key: PROTON-868 URL: https://issues.apache.org/jira/browse/PROTON-868

[jira] [Commented] (PROTON-866) Implement SASL external with TLS client authentication

[ https://issues.apache.org/jira/browse/PROTON-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14511873#comment-14511873 ] Andrew Stitcher commented on PROTON-866: Amongst other things this will require

[jira] [Commented] (PROTON-857) reduce memory usage for the TransportSession link handle tracking

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

[jira] [Commented] (PROTON-853) [proton-j] the transport emitted a new attach frame for a link in the process of being closed

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

[jira] [Commented] (PROTON-850) inconsistent state when reusing link name

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

Re: candidate commits for 0.9.1

Ok ignore all that for now. Andrew has noted a problem with the branch. I seemingly had a stale set of tags and an old 0.9 branch, so when I thought I was branching from the 0.9 tag I was actually not, but rather the 0.9-rc3 tag (which in my case happened to be the same as 0.9, but in an up to

[GitHub] qpid-proton pull request: Mbed minor changes and sasl mech

Github user dcristoloveanu commented on the pull request: https://github.com/apache/qpid-proton/pull/19#issuecomment-95988615 I think this can be merged in now, unless there's anything else that you think needs addressing. Thanks! /Dan --- If your project is set up for

Re: candidate commits for 0.9.1

I branched 0.9.x from the 0.9 tag and cherry picked the commits I mentioned earlier. I have added a 0.9.1 version in JIRA, though I havent yet updated the JIRAs for the commits which had one, I'll get that over the weekend. Here is an updated output from git-cherry of master agaisnt 0.9.x, for

[GitHub] qpid-proton pull request: Mbed minor changes and sasl mech

Github user asfgit closed the pull request at: https://github.com/apache/qpid-proton/pull/19 --- 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

[jira] [Commented] (PROTON-490) [proton-c] Python binding fails to link with Python 3 libraries

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

[jira] [Commented] (PROTON-490) [proton-c] Python binding fails to link with Python 3 libraries

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

[jira] [Commented] (PROTON-490) [proton-c] Python binding fails to link with Python 3 libraries

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

[jira] [Assigned] (PROTON-866) Implement SASL external with TLS client authentication

[ https://issues.apache.org/jira/browse/PROTON-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-866: -- Assignee: Andrew Stitcher Implement SASL external with TLS client authentication

[jira] [Created] (PROTON-866) Implement SASL external with TLS client authentication

Andrew Stitcher created PROTON-866: -- Summary: Implement SASL external with TLS client authentication Key: PROTON-866 URL: https://issues.apache.org/jira/browse/PROTON-866 Project: Qpid Proton

[jira] [Assigned] (PROTON-867) Enable PLAIN SASL mech iff connection is encrypted

[ https://issues.apache.org/jira/browse/PROTON-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher reassigned PROTON-867: -- Assignee: Andrew Stitcher Enable PLAIN SASL mech iff connection is encrypted

[jira] [Created] (PROTON-867) Enable PLAIN SASL mech iff connection is encrypted

Andrew Stitcher created PROTON-867: -- Summary: Enable PLAIN SASL mech iff connection is encrypted Key: PROTON-867 URL: https://issues.apache.org/jira/browse/PROTON-867 Project: Qpid Proton