I am creating a custom MVC style framework from scratch and am at the point where I need to implement the code to control what happens on POST.
At the moment I have a main index.php which acts as a controller and passes data to other controllers such as:
profilecontroller.class.php
forumcontroller.class.php
At the moment I see two options as to where the POST controllers can go ..
First Approach
Firstly for site wide posts such as login that can occur on any page I would use something like this in the very first index.php to redirect all POST to a specific POST controller that then sends the data to a model to be processed:
if($_POST)
//post controller, works on specific form id's
Alternate Approach
The other option I see would be to build the POST identifier into the model construction sections but I don’t think this would be very manageable/wise as they’d always be checked and resulting in more loaded code?
Are there any good/simple examples out there?
I’m creating my mvc to be as light as possible so that’s my reason for going from scratch.
In a RESTful setup, you would normally have a controller for an object, say
news, and then actions such asadd,edit,deleteetc.Within your actions, you should then assert what HTTP method should be used to access the method, if one should be. For example:
Creating a separate controller for POST requests would, as you say, quickly becoming unruly and unmanageable.
If you’re looking for a way of handling requests for different HTTP methods within different controller actions, then maybe check out ToroPHP. It’s a lightweight (single file) router, where you map a request to a class that’s referred to as a handler, and then that handler has methods for different HTTP methods. A quick example:
And then your
HomeHandlerwould look as follows:Hope that helps.