[
https://issues.apache.org/jira/browse/PROTON-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254186#comment-16254186
]
ASF subversion and git services commented on PROTON-1064:
---------------------------------------------------------
Commit 738c1980eff65051163e53ba2f1a64a0ce2672dd in qpid-proton's branch
refs/heads/go1 from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=738c198 ]
PROTON-1658: [ruby] simpler, more portable port allocation for tests
The SO_REUSEADDR trick that works on Linux does not work on OSX or Windows.
Use a simpler approach of listen(0), close socket, do real listen. This is
potentially race-prone but works well in practice
The correct solution is to allow the container to listen using a pre-existing
socket,
this is coming with PROTON-1064.
> ruby: native IO based on connection_driver.c
> ---------------------------------------------
>
> Key: PROTON-1064
> URL: https://issues.apache.org/jira/browse/PROTON-1064
> Project: Qpid Proton
> Issue Type: Improvement
> Components: ruby-binding
> Affects Versions: 0.11.0
> Reporter: Alan Conway
> Assignee: Alan Conway
> Fix For: proton-c-0.19.0
>
>
> Refactor ruby binding to use a native Ruby IO driver with the C
> pn_connection_driver for AMQP protocol support.
> Ruby ConnectionDriver - drive a single connection, single threaded
> - Use any ruby IO subclass
> - Works with native Ruby polling primitives
> - Avoids Ruby threading issue with GVL (all IO is done in Ruby)
> - Thread safe function injection for MT use.
> Client/server examples using native ruby connect, multi-threaded broker
> example using ruby listen.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
