hadoop-zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Hunt (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ZOOKEEPER-661) Add Ruby bindings
Date Mon, 01 Feb 2010 17:48:18 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828196#action_12828196

Patrick Hunt commented on ZOOKEEPER-661:

Hi Andrew, I have no knowledge of ruby extension mechanisms so please keep that in mind wrt
my response. ;-)

We'd love to include a ruby binding in the contrib for zk.

Can you describe, what is the "special threading difficulties" that you mention? Are you using
multi threaded version of the ZK c client library, or the single threaded? It might
be easier for you to integrate if you use the ST version, however you'll need to do a bit
more work. See the
cli.c in trunk/src/c/src of zookeeper for an example of the differences (the THREADED define
in cli.c in particular).

I've been in discussions recently with zkperl users who are looking for async support. The
current binding for 
zkperl only supports sync calls for what sounds like a similar issue to what you are facing.
One option that
sounded promising was switching to use of st rather than mt binding. Please take a look and
let me know if
you have questions (again, cli.c is a good example of what's diff).

> Add Ruby bindings
> -----------------
>                 Key: ZOOKEEPER-661
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-661
>             Project: Zookeeper
>          Issue Type: New Feature
>          Components: contrib-bindings
>         Environment: MRI Ruby 1.9
> JRuby 1.4
>            Reporter: Andrew Reynhout
>            Priority: Minor
> Add Ruby bindings to the ZooKeeper distribution.
> Ruby presents special threading difficulties for asynchronous ZK calls (aget, watchers,
etc).  It looks like the simplest workaround is to patch the ZK C API.
> Proposed approach will be described in comment.
> Please use this ticket for discussion and suggestions.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message