Out of curiosity, but is there a design-reason why the controller names are tied (by naming convention) to HTTP convention?

i.e.

    public static function show_GET($params=null) {	
	self::render('show',array("layout" => "default"));
    }

    public static function index_POST($params=null) {
	self::redirect('/auction/show');
    }

As opposed to how Rails does it (controllers are defined in their own file and associated with a HTTP protocol in a routing file): http://guides.rubyonrails.org/routing.html

in routes file:

     get 'photos/show'

in controller: photos_controller.rb

    class PhotosController < ApplicationController
       def show
          # render stuff
       end
    end

Seems like it's an unnecessary coupling (also, I think in Rails, you don't have to define protocol unless you feel it's explicitly needed), but my main nitpick was seeing a naming convention that featured the kind of letter-case-changing that has made PHP a difficult language to enjoy