Merb devel - Aug 2007 - What makes Rails'' routes non-thread-safe?

I was reading here and there about the differences between Merb and  
Rails [1] and became curious about statements such as this:
> It is threadsafe with configurable Mutex Locks (Routing is also  
> threadsafe)
Having mucked with the routes system, I had this awful feeling that I  
don''t understand threading well enough to know if my contribution is  
"thread safe".  Can someone help me to understand what makes
Merb''s
routes threadsafe while Rails'' is not?  For example, does the late- 
bound procs I''ve added to the new routing system make it
non-threadsafe?

Thanks,

Duane Johnson
(canadaduane)

[1] http://www.infoq.com/news/2007/08/performance-ruby-on-merb
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/merb-devel/attachments/20070829/faca0c23/attachment.html

On Aug 29, 2007, at 9:46 AM, Duane Johnson wrote:
> I was reading here and there about the differences between Merb and  
> Rails [1] and became curious about statements such as this:
>
>> It is threadsafe with configurable Mutex Locks (Routing is also  
>> threadsafe)
>
> Having mucked with the routes system, I had this awful feeling that  
> I don''t understand threading well enough to know if my
contribution
> is "thread safe".  Can someone help me to understand what makes  
> Merb''s routes threadsafe while Rails'' is not?  For
example, does
> the late-bound procs I''ve added to the new routing system make it
> non-threadsafe?
>
> Thanks,
>
> Duane Johnson
> (canadaduane)
>
Duane-

	Mostly the fact that is uses a bunch of alias_method_chain and  
method redefinition. I didn''t dig into to it much further then that.  
I''ll review your new routes to see if I think anything is not safe  
but I think we''re fine.

Cheers-
-- Ezra Zygmuntowicz 
-- Founder & Ruby Hacker
-- ez at engineyard.com
-- Engine Yard, Serious Rails Hosting
-- (866) 518-YARD (9273)