[jira] [Commented] (PROTON-810) Publish javascript binding on npm

[ https://issues.apache.org/jira/browse/PROTON-810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14298773#comment-14298773 ] Matteo Murgida commented on PROTON-810: --- ok, how can I help? can I publish it by

[jira] [Assigned] (PROTON-812) LinkException needs an attribute that indicates the reason for the exception.

[ https://issues.apache.org/jira/browse/PROTON-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reassigned PROTON-812: - Assignee: Gordon Sim LinkException needs an attribute that indicates the reason for the

[jira] [Created] (PROTON-812) LinkException needs an attribute that indicates the reason for the exception.

Jeff Ortel created PROTON-812: - Summary: LinkException needs an attribute that indicates the reason for the exception. Key: PROTON-812 URL: https://issues.apache.org/jira/browse/PROTON-812 Project: Qpid

[jira] [Resolved] (PROTON-809) Changes to build on AIX with IBM XL C

[ https://issues.apache.org/jira/browse/PROTON-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Huston resolved PROTON-809. - Resolution: Fixed Fix Version/s: 0.9 Changes to build on AIX with IBM XL C

Ruby, Proton Engine and Records

So over the last week I've been working on a way to avoid leaking memory or causing segfaults when the underlying C library is giving a reference to a Ruby object. And after much coding and gnashing of teeth I foudn the easiest way to do this with manually wrapping the pn_record_t struct. That

[jira] [Commented] (PROTON-809) Changes to build on AIX with IBM XL C

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

Re: Ruby memory management (was: Ruby and the Engine APIs)

On Wed, Jan 28, 2015 at 01:22:45PM -0500, Rafael Schloming wrote: snip Also, have you been able to validate your testing strategy for either/both of these POCs? Can you generate seg faults and/or valgrind warnings when you intentionally comment out the line of code that keeps the reference

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14298501#comment-14298501 ] Rafael H. Schloming commented on PROTON-811: Looks good! One further tweak

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14298521#comment-14298521 ] Adrian Preston commented on PROTON-811: --- Once again, thanks for the quick feedback.