> Can you make a small proof of concept patch that we can benchmark a > bit and then decide?
Attached is a patch which implements the controller exception api. It's hacky and not meant for production. In merb_exceptions.rb is the definition of Merb::ControllerExceptions::Base. That is an abstract base class. Derived from Base are a bunch of other classes: class NoContent < Base; STATUS = 204; end class ResetContent < Base; STATUS = 205; end class PartialContent < Base; STATUS = 206; end class MultipleChoices < Base; STATUS = 300; end To use this, one would derive a class from one of these and write a method :merb_action (i didn't use :action because of name conflicts) which should work more or less like a typical controller action. The patch contains specs showing it in action with render :layout This should be enough to benchmark? The erb file for MyException#merb_action is looked for at app/views/exceptions/my_exception.erb ry
controller_exceptions.diff
Description: Binary data
_______________________________________________ Merb-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/merb-devel
