Comments on: How to avoid the dog-pile effect on your Rails app

By: José Valim

José Valim — Wed, 14 Oct 2009 12:49:11 +0000

@Thomas, for Rails’ auto load to work, you have to use all the namespaces in your class, so you have to put it under: app/lib/active_support/cache/smart_mem_cache_store.rb.

If you want to have it hanging at app/lib/smart_mem_cache_store.rb, you can require the file manually, instead of relying on Rails autoload.

By: José Valim

José Valim — Wed, 14 Oct 2009 12:49:00 +0000

@Thomas, for Rails’ auto load to work, you have to use all the namespaces in your class, so you have to put it under: app/lib/active_support/cache/smart_mem_cache_store.rb.

If you want to have it hanging at app/lib/smart_mem_cache_store.rb, you can require the file manually, instead of relying on Rails autoload.

By: Thomas Hanley

Thomas Hanley — Tue, 13 Oct 2009 17:53:49 +0000

I get issues trying to start up the application with this in my lib.

/Workspace/lc_dev/lib/smart_mem_cache_store.rb to define SmartMemCacheStore

In my development.rb:
config.cache_store = :smart_mem_cache_store

In environments.rb:
cache = ActiveSupport::Cache::MemCacheStore.new(fragment_memcache_servers,shared_memcache_options.merge(:namespace => “fragment”))
self.action_controller.cache_store = cache, {}

I tried putting ActiveSupport::Cache::SmartMemCacheStore and I get the same error.

By: Thomas Hanley

Thomas Hanley — Tue, 13 Oct 2009 17:53:00 +0000

I get issues trying to start up the application with this in my lib.

/Workspace/lc_dev/lib/smart_mem_cache_store.rb to define SmartMemCacheStore

In my development.rb:
config.cache_store = :smart_mem_cache_store

In environments.rb:
cache = ActiveSupport::Cache::MemCacheStore.new(fragment_memcache_servers,shared_memcache_options.merge(:namespace => “fragment”))
self.action_controller.cache_store = cache, {}

I tried putting ActiveSupport::Cache::SmartMemCacheStore and I get the same error.

By: José Valim

José Valim — Fri, 11 Sep 2009 09:39:23 +0000

@pete we usually lay code on lib/. initializers we use for configuration and for code that should be loaded while rails is loaded (aka monkey patches).

@walter we cannot use super because we need to access the orig_write inside read.

By: José Valim

José Valim — Fri, 11 Sep 2009 09:39:00 +0000

@pete we usually lay code on lib/. initializers we use for configuration and for code that should be loaded while rails is loaded (aka monkey patches).

@walter we cannot use super because we need to access the orig_write inside read.