mvc controller single responsibility principle and POST requests
In general case you will want to have a separate controller for each 'type' of request. This helps in keeping the code simple, without having to deal with any 'special cases', and in general easier to reuse.
I am interested in the correct/standard/advised approach for an django web application I am currently developing.
I have practical experience in programming, but I am worried about the efficiency of my implementation, since I don't have too much theoretical knowledge of MVC and related principles.
I have several forms that must fetch various amounts of information from my database (via AJAX POST requests), all related to a single action the user would take (for example: to buy a house, the system would need information about the house, the client, the previous owner, the method of payment, etc.).
Because of this, the POST requests would be very frequent in one page.
My question is: 
should I have one controller responsible for each different "type" of POST request (one controller for the "house" requests, one for the "client", etc.), or is it ok to have one "sale data fetcher" controller that handles all related POST requests checks via one of the parameters of each request and communicate with the model accordingly?
I apologize if am not using the question system correctly, this is my first question here.
EDIT: total lapse in my question!!! Yes the App is in PYTHON, I did use PHP for a previous Project.
Thanks in advance! stack overflow has been a lifesaver so many times.