José Valim 11bc3487ab Remove allow_concurrency as a flag ... The flag was mainly used to add a Rack::Lock middleware to the stack, but the only scenario the lock is desired is in development. If you are deploying on a not-threaded server, the Rack::Lock does not provide any benefit since you don't have concurrent accesses. On the other hand, if you are on a threaded server, you don't want the lock, since it defeats the purpose of using a threaded server. If there is someone out there, running on a thread server and does want a lock, it can be added to your environment as easy as: `use Rack::Lock`		2012-08-21 14:46:12 -03:00
..
assets	Merge pull request #6383 from oscardelben/add_oscardelben_to_authors	2012-05-23 10:49:06 -07:00
code/getting_started	Remove `:confirm` in favor of `:data => { :confirm => 'Text' }` option	2012-07-18 10:32:17 -03:00
rails_guides	removes usage of Object#in? from the code base (the method remains defined by Active Support)	2012-08-06 00:30:02 +02:00
source	Remove allow_concurrency as a flag	2012-08-21 14:46:12 -03:00
Rakefile	[guides] guides:generate:kindle is the new interface to generate .mobi file instead of using KINDLE=1	2012-05-28 16:20:10 -05:00
rails_guides.rb	Remove remaining require 'rubygems'	2012-05-13 13:33:20 -03:00
w3c_validator.rb	Remove remaining require 'rubygems'	2012-05-13 13:33:20 -03:00