1. 05 1月, 2013 3 次提交
  2. 26 12月, 2012 1 次提交
  3. 22 12月, 2012 1 次提交
  4. 11 12月, 2012 1 次提交
  5. 08 12月, 2012 2 次提交
  6. 30 11月, 2012 1 次提交
  7. 29 11月, 2012 2 次提交
  8. 11 11月, 2012 1 次提交
  9. 04 11月, 2012 2 次提交
  10. 29 10月, 2012 1 次提交
  11. 18 10月, 2012 2 次提交
  12. 17 10月, 2012 2 次提交
  13. 13 10月, 2012 1 次提交
  14. 06 10月, 2012 3 次提交
  15. 20 9月, 2012 1 次提交
  16. 18 9月, 2012 8 次提交
  17. 15 9月, 2012 1 次提交
  18. 13 9月, 2012 1 次提交
  19. 03 9月, 2012 1 次提交
  20. 25 8月, 2012 1 次提交
  21. 22 8月, 2012 3 次提交
    • J
      Deprecate config.threadsafe! · 5d416b90
      José Valim 提交于
      5d416b90
    • J
      Get rid of config.preload_frameworks in favor of config.eager_load_namespaces · 2801786e
      José Valim 提交于
      The new option allows any Ruby namespace to be registered and set
      up for eager load. We are effectively exposing the structure existing
      in Rails since v3.0 for all developers in order to make their applications
      thread-safe and CoW friendly.
      2801786e
    • J
      Remove allow_concurrency as a flag · 11bc3487
      José Valim 提交于
      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`
      11bc3487
  22. 19 8月, 2012 1 次提交