From: Christian Neukirchen <chneukirchen@...>
Date: 2005-09-12T03:33:32+09:00
Subject: Re: [RFC] The Early Demise of Myriad (Thanks To Ruby Threads)

"Zed A. Shaw" <zedshaw@zedshaw.com> writes:

> This basically means that, I have three choices as I see it:
>
> 	1) Ruby/Event becomes completely evil and redefines Thread's
> 	initialize so that it throws an exception telling you to not
> 	use threads.  Ugh.

> 	2) Implement DRb using Myriad so that people can get the
> 	advantages of threads without using them.  Also ugh.  No
> 	protocol specs does not make for a fun time implementing a
> 	protocol.  And no, source code is *not* a protocol
> 	specification.

> 	3) Abandon Ruby/Event entirely and just base a new
> 	implementation of Myriad on the Ruby thread stuff.  I know you
> 	purists will think this is great, but you do realize that I
> 	get *incredible* performance from libevent and that a pure
> 	Ruby implementation would only handle as many connections as
> 	select supports (which is sometimes 256)?

Or,     4) Become a great Ruby hacker and replace the Ruby thread select()
        completely with libevent. ;-)

> Thanks for your time and your opinion.
>
> Zed A. Shaw
-- 
Christian Neukirchen  <chneukirchen@gmail.com>  http://chneukirchen.org