SessionsHelper in railstutorial.org: Should helpers be general-purpose modules for code not needed in views?
railstutorial.org has a suggestion which strikes me as a little odd. It suggests this code : class ApplicationController < ActionController::Base protect_from_forgery include SessionsHelper end The include SessionsHelper makes the methods available from ApplicationController , yes, but it makes them available in any view, as well. I understand that authentication/authorization is cross-cutting, but is this really the best place? That seems to me to be potentially too broad of a scope. Putting code which implements, say, a before_filter which conditionally redirects (as the railstutorial.org