Re: [Jruby-devel] Another socket patch

2006-04-30 Thread Thomas E Enebo
On Sun, 30 Apr 2006, Evan Buswell defenestrated me: > > The select() in question is on TCPServer objects, so doing a workaround > with InputStream.available isn't going to work. As far as I can tell, we > need to break out nio. Yep. As Charlie noted, we need nio. It is just a matter of time.

Re: [Jruby-devel] Another socket patch

2006-04-30 Thread Charles O Nutter
If you were to tackle a NIO IOHandler, you'd be a lot of people's hero. The move to NIO is not a maybe, it's a must...there's simple too much in Ruby we can't implement without it. We've already started to use NIO in a few places for things like file locking, so we're on the way there already. In

Re: [Jruby-devel] Another socket patch

2006-04-30 Thread Evan Buswell
Poking around a bit more, I defined AI_PASSIVE to some dummy value and now WEBrick::GenericServer runs up to the point of select(...). Of course, this is no big deal since we already knew it was going to fail on select and that's the sticky point here anyway. The select() in question is on TCPSer

Re: [Jruby-devel] Another socket patch

2006-04-28 Thread Thomas E Enebo
I will take a look this weekend. Anything which gets us closer is a great thing. When I examined sockets last, it seemed there would need to be quite a few caveats since Java sockets are a little more abstracted than all other socket libraries (hence the mismatch). The biggest pain in theor