On Tue, 2006-12-26 at 19:43 -0300, Luis Lavena wrote: > I guess rubygems folks added thread part of rubygems now... something > that isn't good at all (why I require thread if my application I don't > use it?, just to say something).
I don't know... it seems reasonable if they need to do something in a threadsafe manner. Even e.g. Singleton needs synchronization, though it doesn't currently use Mutex to do it (IMO it _should_, fastthread weirdness aside). I'm not really sure what the best resolution here is. fastthread is ultimately intended to become a patch to Ruby core, of course. But that can't happen immediately, especially as even with the patch in hand I would still need to sell the ruby-core folks on it... -mental
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
