By rights, when you spawn a separate thread, if it blocks that shouldn't affect other threads. That that is not how it works with the Win32 Ruby. (The unix ruby, including the cygwin ruby work correctly.)
So if you do something that is going to block a thread, like say click a button that brings up a dialog, you have to make sure that either A. You click the button in a separate process (not just a thread), and then click the button in the current process. or B. You start up a process that will click the button when it appears, then you click the button, causing the current thread to block. I don't think that DRB provides a workaround for this clumsiness. Because once a process is blocked, it is blocked. DRB is synchronous. Bret _____________________ Bret Pettichord www.pettichord.com _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
