Re: proton-j/proton-c integration primer

Rafael Schloming-3 wrote These projects aren't actually quite as independent as they look. There is a common test suite that runs against both implementations to help keep them in sync with each other. This is the python test suite that lives underneath the top level tests/python directory.

Re: proton-j/proton-c integration primer

On Tue, Feb 3, 2015 at 6:32 AM, Dominic Evans dominic.ev...@uk.ibm.com wrote: Rafael Schloming-3 wrote These projects aren't actually quite as independent as they look. There is a common test suite that runs against both implementations to help keep them in sync with each other. This is

[jira] [Created] (PROTON-814) proton-c: pn_selector_select caches its return code from a previous error

Dominic Evans created PROTON-814: Summary: proton-c: pn_selector_select caches its return code from a previous error Key: PROTON-814 URL: https://issues.apache.org/jira/browse/PROTON-814 Project:

[jira] [Commented] (PROTON-814) proton-c: pn_selector_select caches its return code from a previous error

[ https://issues.apache.org/jira/browse/PROTON-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14304103#comment-14304103 ] ASF GitHub Bot commented on PROTON-814: --- GitHub user dnwe opened a pull request:

[jira] [Commented] (PROTON-814) proton-c: pn_selector_select caches its return code from a previous error

[ https://issues.apache.org/jira/browse/PROTON-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14304106#comment-14304106 ] ASF GitHub Bot commented on PROTON-814: --- Github user dnwe commented on the pull

[jira] [Updated] (PROTON-811) [PATCH] proton-j: no way to implement idle timeout of a connection

[ https://issues.apache.org/jira/browse/PROTON-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrian Preston updated PROTON-811: -- Attachment: 0001-proton-j-updates-for-idle-timeout-mk4.patch Reworked the patch to fix

[jira] [Assigned] (PROTON-757) [PATCH] proton-c: transport errors are output to stderr in 0.8 onwards

[ https://issues.apache.org/jira/browse/PROTON-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans reassigned PROTON-757: Assignee: Dominic Evans [PATCH] proton-c: transport errors are output to stderr in 0.8

[jira] [Commented] (PROTON-757) [PATCH] proton-c: transport errors are output to stderr in 0.8 onwards

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

Re: Non-reactive engine examples?

On Mon, Feb 02, 2015 at 09:12:22AM -0500, Darryl L. Pierce wrote: Are there any example apps for Python that don't use the reactive APIs? If no examples, perhaps a primer of how the logical components of the enger interact to help guide providing an example? -- Darryl L. Pierce, Sr. Software

[jira] [Closed] (PROTON-757) [PATCH] proton-c: transport errors are output to stderr in 0.8 onwards

[ https://issues.apache.org/jira/browse/PROTON-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans closed PROTON-757. [PATCH] proton-c: transport errors are output to stderr in 0.8 onwards

[jira] [Closed] (PROTON-751) [PATCH] proton-c: pn_connect failures aren't exposed via messenger-error

[ https://issues.apache.org/jira/browse/PROTON-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans closed PROTON-751. [PATCH] proton-c: pn_connect failures aren't exposed via messenger-error

[jira] [Resolved] (PROTON-757) [PATCH] proton-c: transport errors are output to stderr in 0.8 onwards

[ https://issues.apache.org/jira/browse/PROTON-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans resolved PROTON-757. -- Resolution: Fixed Fix Version/s: 0.9 Pushed under 78e54ee [PATCH] proton-c: transport

[jira] [Assigned] (PROTON-751) [PATCH] proton-c: pn_connect failures aren't exposed via messenger-error

[ https://issues.apache.org/jira/browse/PROTON-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans reassigned PROTON-751: Assignee: Dominic Evans [PATCH] proton-c: pn_connect failures aren't exposed via

[jira] [Resolved] (PROTON-751) [PATCH] proton-c: pn_connect failures aren't exposed via messenger-error

[ https://issues.apache.org/jira/browse/PROTON-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans resolved PROTON-751. -- Resolution: Fixed Fix Version/s: 0.9 fixed in b9423d4 [PATCH] proton-c: pn_connect

[jira] [Commented] (PROTON-751) [PATCH] proton-c: pn_connect failures aren't exposed via messenger-error

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