Mauricio Fernández
10/7/2004 9:57:00 PM
On Fri, Oct 08, 2004 at 06:24:42AM +0900, James Edward Gray II wrote:
> On Oct 7, 2004, at 3:44 PM, Jeff wrote:
>
> >So what is the state of the world with the various options that exist
> >in Ruby for this sort of thing? I've had a brief look at rjni, rjava
> >and rjb.
rjb is the only one actively developed atm., so it's probably the best
option.
I stopped working on rjni when I discovered that the JVM was interacting
with the signals ruby uses to implement threads (so that Ruby threads
wouldn't work) and realized that the non-reentrancy of ruby 1.x made
this all quite hard...
> Each of which seem to be quite 'alpha'. Any comments,
> >suggestions on which is best? Any other options in terms of design?
> >Will these work with network/socket classes in Java?
The main problem would be when you have multiple Java threads; that's
hard to handle in 1.x, at least if you're using JNI directly.
--
Running Debian GNU/Linux Sid (unstable)
batsman dot geo at yahoo dot com