Hassan Schroeder wrote in post #1012506:
> But certainly the default Rails configuration *appears* to be single-
> threaded.

It is - not because of an inherent limitation of webrick, but because 
Rails itself has a global dispatcher lock. This dates from the days when 
Rails internals were not thread-safe. They are now, but because your 
application may not be thread safe, the global lock remains unless you 
give a configuration command to turn it off. Google "rails config 
threadsafe"

Normally it doesn't matter in production, because you're running 
multiple server processes (e.g. mongrels, passenger workers etc) behind 
some sort of proxy, and you only want each one to be handling one 
request at a time.

-- 
Posted via http://www.ruby-forum.com/.