search

sekharnbos / activemessaging

Automatically exported from code.google.com/p/activemessaging
0 stars 0 forks source link

Rails 2.1 improperly prepared in production mode #38

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Currently activemessaging reloads the Rails application between every
message regardless of the cache_classes configuration setting.  This
results in an unnecessary performance hit in production mode because
all classes must be reloaded from disk after for each message.

Additionally, this behavior confuses ActiveSupport::Dependency in a
way that make classes in sub-directories unloadable once the
application has been reloaded once.  If you have classes in
sub-directories the first message received will work correctly, but
all subsequent messages cause a LoadError.  The LoadError only occurs
when is cache_classes is true because the dependency management system
does not expect to be reset unless that configuration item is set to
false.

Original issue reported on code.google.com by pe...@barelyenough.org on 23 Sep 2008 at 4:05

GoogleCodeExporter commented 8 years ago 
Patch which takes cache_classes configuration item into account.  This patch 
only
implements this for Rails 2.1+.  Similar issues might exist in older versions of
Rails.  If that is true this patch would probably not correct those issues.

Original comment by pe...@barelyenough.org on 23 Sep 2008 at 4:11

Attachments: