I want to create fault-tolerant, self healing web application. It means, situation when the application fails (with some weird errors on the screen) should be *unacceptable*. Every exception should be captured and handled by the application.
Everybody knows this is impossible in PHP (fatal errors cannot be captured by any code). But not everybody aware that Rails is like PHP here. If MySQL is down, Rails application raises exception which.... cannot be handled by any its controllers. This exception is not propagated to them at all by the framework. I even created a ticket http://bit.ly/cIQRTy thinking this was Rails 3.0RC only error. But afterwards, I found Rails 2.3.8 "works" in the same way. It looks like that error is in all Rails versions. We have Rails 3.0 RC now and Rails 3.0 final is almost there. And I hope Merb will still be continued and never disapear after Rails 3.0 final is relased... -- JZ -- You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/merb?hl=en.
