diff options
| author | José Valim <jose.valim@gmail.com> | 2012-08-01 15:27:57 +0200 |
|---|---|---|
| committer | José Valim <jose.valim@gmail.com> | 2012-08-21 14:46:12 -0300 |
| commit | 11bc3487ab0a9a99de2542f0aa2777c88c7c2198 (patch) | |
| tree | 23eb11aaaa1eae76dd434fcc98cb49e267d1f0ca /activesupport/lib/active_support/dependencies | |
| parent | e6747d87f3a061d153215715d56acbb0be20191f (diff) | |
| download | rails-11bc3487ab0a9a99de2542f0aa2777c88c7c2198.tar.gz rails-11bc3487ab0a9a99de2542f0aa2777c88c7c2198.tar.bz2 rails-11bc3487ab0a9a99de2542f0aa2777c88c7c2198.zip | |
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`
Diffstat (limited to 'activesupport/lib/active_support/dependencies')
0 files changed, 0 insertions, 0 deletions