I just realized -- if fastthread can be included while Mutex-using code is already running, then the definition and replacement of the classes needs to happen atomically. Otherwise, it creates a race condition where a thread can e.g. end up seeing an incompletely defined Mutex class or none at all.
fastthread 0.6.1 addresses this by defining the classes and then atomically swapping the constant definitions as a final step. -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
