From: "Brian F. Feldman" <green@...>
Date: 2001-04-28T11:13:08+09:00
Subject: [ruby-talk:14362] Re: Ruby vs. Tcl input/output question

Mathieu Bouchard <matju@sympatico.ca> wrote:
> On Fri, 27 Apr 2001, Yukihiro Matsumoto wrote:
> > |* Tcl-Eventloop:
> > |   the greatest thing of Tcl is for sure the Eventloop which
> > |   combines File/Pipe/Socket readable/writeable-events AND Tk-GUI
> > |   AND 'decoupled callbacks' via [after <time> command]
> > |   I could not find such a thing in Ruby (where to look?)
> > Ruby chooses thread model.  So
> >   Thread.start{
> >     sleep <time>
> >     <command>
> >   }
> > would do without 'event loops'.
> 
> Whatever "Ruby" (or you) chooses, I choose the non-thread model, because
> then I don't have to worry about locking; and because of that, I don't
> have to worry about deadlocks, livelocks, and locking latencies. Instead I
> worry about granularity of event operations, which I believe to be more
> manageable on average. 
> 
> Well, in case anyone cares, I have written an event loop, and I could
> publish it if someone asks for it.

And if anyone else is interested, I've written a decent-sized threaded 
server application in the form of Bonkle...  I'd like to clean up the manner 
the locking is done in, but I paid lots of care to not have races and to do 
everything efficiently.  See:
	http://green.bikeshed.org/~green/bonkle-011.tar.gz

BTW, I have half of a client written and the server only needs a bit more, 
like "operator" status and whatnot, so if anyone wants to help me finish it 
;)


-- 
 Brian Fundakowski Feldman           \  FreeBSD: The Power to Serve!  /
 green@FreeBSD.org                    `------------------------------'