Topper Bowers commented on ZOOKEEPER-661:

I've been hacking on this too: 

I've basically taken everybody else's work and modified and combined to make 
something that's "getting there."  I'm not a fan of the FFI method as it can 
cause issues.  Also, Solaris (our prod env) seems to really dislike it.

My branch here has an MRI that can synchronously write/read (without watches 
and without eventmachine).  If you add in event machine, watches are enabled.
Jruby (our other prod env) one should theoretically support all the async and 
watchers out of the box.

Added some sugar: queues and lockers (lockers can be used without watches).

People think I'm on the right track here?

> 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.

Reply via email to