[
https://issues.apache.org/jira/browse/PROTON-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14287347#comment-14287347
]
Rafael H. Schloming commented on PROTON-804:
I believe this is a release
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 anyone using this code in anyway? I would
like to at a minimum
On Thu, Jan 22, 2015 at 10:50:22AM -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
[
https://issues.apache.org/jira/browse/PROTON-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-800.
-
Resolution: Fixed
Fix Version/s: 0.9
Assignee: Cliff Jansen
As per the other
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.
As I've said before, the first step to wrapping the engine API is to work
out a simple strategy for wrapping C
Yes, those are part of the driver API.
--Rafael
On Thu, Jan 22, 2015 at 11:08 AM, Darryl L. Pierce dpie...@redhat.com
wrote:
On Thu, Jan 22, 2015 at 10:50:22AM -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
[
https://issues.apache.org/jira/browse/PROTON-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14287893#comment-14287893
]
Rafael H. Schloming commented on PROTON-804:
rschloming: basically what
