From: "Radosław Bułat" <radek.bulat@...>
Date: 2008-01-20T03:46:48+09:00
Subject: Re: [ANN] Thin 0.5.3 Purple Yogurt release

Of course it depends on specific situation but in about 99% situations
you should log error and give message to user describing what was
wrong (it could be even well known rails message "something went
wrong" ;)). Of course there exceptions that you should explicitly
rescue and exceptions that are very generic to catch every time.

For example, when I implement authentication I do:
def signin
  user = User.authenticate(params[:login], params[:password])
  #(...)
rescue User::AuthenticationException
  flash[:error] = "error message"
end

But of course I can make mistake somewhere and for example I could get
exception because I call method on nil object  (NoMethodError
exception). In this situation you can use rails handling exceptions
mechanism (Ryan Bates to the rescue -
http://railscasts.com/episodes/53).

So for global handling you can write:
def rescue_action(exception)
    case exception
    when NoMethodError
      render :text => "ups..."
    else
      super
    end
end

-- 
Rados³aw Bu³at

http://radarek.jogger.pl - mój blog