search for: memcachestor

...o take advantage of the latest fun, I get the following error-message at startup time. rails@lists.rubyonrails.org $ ruby script/process/respawn ..... ... /vendor/rails/activerecord/lib/../../activesupport/lib/active_support/dependencies.rb:125:in `const_missing'': uninitialized constant MemCacheStore (NameError) Did anybody come across this? How did you fix it? Thanks, -Armin -- http://www.approximity.com Agile blog: http://agile.approximity.com Risk Management blog http://risk.approximity.com

When pass :cache param to ActionDispatch::Session::MemCacheStore, it should be removed from options, otherwise it remains "published". This violates the OOP encapsulation principle. I created a LH ticket with a patch http://bit.ly/cGDaWs Luca -- lucaguidi.com twitter.com/jodosha -- You received this message because you are subscribed to the Googl...

Hi all - I am trying to get rails to use memcache for sessions and fragment caching. I''d also like to use the same connection for general caching of this and that. I''m following the instructions here: http://wiki.rubyonrails.com/rails/pages/HowtoChangeSessionStore and hitting a brick wall. I''m using the new memcache-client since from what I''ve read

...ils/tickets/4452 I have recently been working on some gems that utilize ActiveSupport::Cache and ran into some issues with the different implementations handling the same functionality differently. One of the issues was that I couldn''t rely on expiring entries with the :expires_in option. MemCacheStore takes this option on a write, while FileStore takes it on a read, and MemoryStore ignores it all together so that the cache will just grow until you run out of memory. I ended up doing a pretty large refactoring of ActiveSupport::Cache to provide universal support for some options, fix some bugs,...

...n => true, :debug => false, :namespace => ''ruby-forum.com'', :readonly => false, :urlencode => false } CACHE = MemCache.new memcache_options CACHE.servers = ''localhost:11211'' session_options = { :database_manager => CGI::Session::MemCacheStore, :cache => CACHE, :session_domain => ''ruby-forum.com'' } ActionController::CgiRequest::DEFAULT_SESSION_OPTIONS.update session_options <<<<<<<<<<<<<<<<<<<<<<<<< Bur Rails still uses the sessio...

...debug => false, :namespace => ''my_rails_app'', :readonly => false, :urlencode => false } CACHE = MemCache.new memcache_options CACHE.servers = ''localhost:11211'' session_options = { :database_manager => CGI::Session::MemCacheStore, :cache => CACHE, :session_domain => ''trackmap.robotcoop.com'' } ActionController::CgiRequest::DEFAULT_SESSION_OPTIONS.update session_options You will need separate namespaces for production and development, if using memcache on the same machine. Note...

Facebook''s new session format contains periods and underscores which appear to be breaking mem_cache_store. To get my app working again, I appended the following code to the end of environment.rb class CGI class Session class MemCacheStore def check_id(id) #:nodoc:# id = id.gsub(''-'', '''').gsub(''.'', '''').gsub(''_'', '''') /[^0-9a-zA-Z-]+/ =~ id.to_s ? false : true end end end end The above code tricks rails into...

...debug => false, :namespace => ''my_rails_app'', :readonly => false, :urlencode => false } CACHE = MemCache.new memcache_options CACHE.servers = ''localhost:11211'' session_options = { :database_manager => CGI::Session::MemCacheStore, :cache => CACHE, :session_domain => ''trackmap.robotcoop.com'' } ActionController::CgiRequest::DEFAULT_SESSION_OPTIONS.update session_options You will need separate namespaces for production and development, if using memcache on the same machine. Note...

Doing some reading up on fragment cache before implmenting it and had a few questions: 1.) I read that page and action caching have issues or don''t work at all with query strings (more so with page caching). Does fragment caching work with query strings? i.e something like example.com/foo/bar?page=2 2.) If the above is true and I have an authentication system built into my app, if 2

...:debug => true, :namespace => ''eztrip'', :readonly => false, :urlencode => false CACHE.servers = ''127.0.0.1:11211'' session_options = { :database_manager => CGI::Session::MemCacheStore, :cache => CACHE, :session_domain => ''www.eztrip.com'' } ActionController::CgiRequest::DEFAULT_SESSION_OPTIONS.update session_options I also changed a few models to extend CachedModel but am having trouble getting it to work. I can manually put things in the cache an...

Could someone please elaborate on the technical differences and practical impact of whether choosing memory-based tables in MySQL or using memcached. I got this far on my own: It seems that MySQL uses the NDB engine for transaction-safe memory access in a cluster. the memory storage engine seems to be faster but not synchronizable by any means in a cluster. memcached seems to be ultimately fast

Greetings, I''m getting this - ActiveModel::MissingAttributeError: missing attribute: some_attr - on a random basis under a unicorn server, running rails 3.2 and ruby 1.9.3 As the case of the last poster in the following thread - https://github.com/rails/rails/issues/1906 - I too am able to resolve this issue by settingpreload_app to false. However, this is not the behaviour I want to

Hi! Before Rails 2.0 is coming, I suggest not to make CookieStore the default session storage. It stores clear-text values on the client-side and the integrity check hash can be brute-force attacked. I understand that this has been set due to speed advantages, but I believe it''s better to make better security a default. I''ve written a blog post about this