[jira] [Assigned] (PROTON-805) Add dispatch request-response extension to utils.py

2015-01-23 Thread Alan Conway (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway reassigned PROTON-805: -- Assignee: Alan Conway Add dispatch request-response extension to utils.py

[jira] [Created] (PROTON-805) [proton python] Add dispatch request-response extension to utils.py

2015-01-23 Thread Alan Conway (JIRA)
Alan Conway created PROTON-805: -- Summary: [proton python] Add dispatch request-response extension to utils.py Key: PROTON-805 URL: https://issues.apache.org/jira/browse/PROTON-805 Project: Qpid Proton

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

2015-01-23 Thread Darryl L. Pierce
On Fri, Jan 23, 2015 at 11:02:59AM -0500, Rafael Schloming wrote: snip For more info on how to integrate with Ruby's GC you can read this article[1]. It's one of the few pieces of documentation I've found that actually explain how to keep a reference from C to a Ruby object. [1]

Re: removing the proton driver API

2015-01-23 Thread Andrew Stitcher
On Thu, 2015-01-22 at 10:50 -0500, Rafael Schloming wrote: I just noticed that dispatch seems to have it's own copy of driver.c now. I think that means the driver API is now dead code as messenger, the new reactor stuff, etc all use the newer selector API. Is anyone else using/aware of

Re: [java] Message codec improvements

2015-01-23 Thread Rajith Muditha Attapattu
Given the existing encorder was not put behind any sort of interface (the impl is directly used), it's proving to be a PIA to track down all the different types and changing them to use the new codec. Look at the public static void register(Decoder decoder, EncoderImpl encoder) method of any of

[jira] [Updated] (PROTON-805) Add dispatch request-response extension to utils.py

2015-01-23 Thread Alan Conway (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-805: --- Summary: Add dispatch request-response extension to utils.py (was: [proton python] Add dispatch

Request for inclusion in 0.9 release

2015-01-23 Thread Alan Conway
Sorry, I'm behind on this but - I have some small but very useful extensions to the new proton/utils.py that are used in dispatch. I would VERY much like to get them into proton 0.9. I will get them on master ASAP, is there another branch they need to go on? Cheers, Alan.

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

2015-01-23 Thread Rafael Schloming
It does talk about what swig does, but it also talks about the other direction: If the C structure references other ruby objects, then the mark function pointer must also be provided and must properly mark the other objects with rb_gc_mark() --Rafael On Fri, Jan 23, 2015 at 1:24 PM, Darryl L.

Re: Request for inclusion in 0.9 release

2015-01-23 Thread Rafael Schloming
On Fri, Jan 23, 2015 at 12:18 PM, Alan Conway acon...@redhat.com wrote: Sorry, I'm behind on this but - I have some small but very useful extensions to the new proton/utils.py that are used in dispatch. I would VERY much like to get them into proton 0.9. I will get them on master ASAP, is

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

2015-01-23 Thread Rafael Schloming
On Fri, Jan 23, 2015 at 2:08 PM, Darryl L. Pierce dpie...@redhat.com wrote: On Fri, Jan 23, 2015 at 01:49:34PM -0500, Rafael Schloming wrote: It does talk about what swig does, but it also talks about the other direction: If the C structure references other ruby objects, then the mark

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

2015-01-23 Thread Darryl L. Pierce
On Fri, Jan 23, 2015 at 01:49:34PM -0500, Rafael Schloming wrote: It does talk about what swig does, but it also talks about the other direction: If the C structure references other ruby objects, then the mark function pointer must also be provided and must properly mark the other objects

[jira] [Commented] (PROTON-805) Add dispatch request-response extension to utils.py

2015-01-23 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14289952#comment-14289952 ] ASF subversion and git services commented on PROTON-805: Commit

Proton 0.9 alpha 2

2015-01-23 Thread Rafael Schloming
Hi Everyone, I've put together an alpha 2 for Proton 0.9. I believe the memory issues identified in alpha 1 are addressed. Source and binaries are posted in the usual locations: Source artifacts: http://people.apache.org/~rhs/qpid-proton-0.9-alpha-2/ Java binaries:

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

2015-01-23 Thread Darryl L. Pierce
On Fri, Jan 23, 2015 at 03:25:33PM -0500, Rafael Schloming wrote: On Fri, Jan 23, 2015 at 2:08 PM, Darryl L. Pierce dpie...@redhat.com wrote: On Fri, Jan 23, 2015 at 01:49:34PM -0500, Rafael Schloming wrote: It does talk about what swig does, but it also talks about the other

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

2015-01-23 Thread Darryl L. Pierce
On Thu, Jan 22, 2015 at 12:08:52PM -0500, Rafael Schloming wrote: The most important thing to get worked out for this is the memory management semantics between C and Ruby. From what I can tell from your branch, it looks like you haven't done that yet. snip My initial readings into how Ruby

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

2015-01-23 Thread Rafael Schloming
That sounds like progress, but from what you're describing I'm not sure you're actually testing C holding onto a reference to Ruby. As you say, swig is helping you out with the Ruby - C direction, but we need to be able to make that void * reference actually point to a ruby object (that is not