search

0xcodezero / activemessaging

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

Should not reload classes after processing each message: #40

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Currently, the code in support.rb causes rails to reload classes each time
a message is processed. It does not respect the value of
config.cache_classes. This causes significant performance issues in
production mode.  

A new support.rb is attached that does not have this problem. It reuses the
callback chain created by the dispatcher, instead of calling the methods
directly. This works on rails 2.2.2, have not tested on any other versions.

Original issue reported on code.google.com by woodh...@gmail.com on 7 Jan 2009 at 8:57

Attachments:

GoogleCodeExporter commented 9 years ago 
I have applied this patch - if someone complains about needing older rails 
version
support, I'll figure that out the (the prior version tried pretty hard to be
compatible back to 1.X)

Original comment by kooks...@gmail.com on 10 Jun 2009 at 3:55