Although our site is
not running in Ruby, yet, we have worked through a number of approaches
to handling this, but only one has the desired properties we need,
which is automatic recovery and minimal impact to running code on
failure: exec out another process to do image manipulation.

I must admit that we do the same thing at 37signals. But actually not because of memory leaks, but because we found it easier to do:

    def thumbnail(temp, target)
      system "convert #{escape(temp)} -resize 48x48! #{escape(target)}"
    end

Rather than to get the full RMagick machinery cooking.
--
David Heinemeier Hansson
http://www.37signals.com -- Basecamp, Campfire, Backpack, Getting Real
http://www.rubyonrails.com  -- Web-application framework
http://www.loudthinking.com -- Broadcasting Brain


Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users

Reply via email to