As already documented above, this is the Controller (aka Listener) that the OECGI immediately calls when it receives an HTTP request. It is a replacement to RUN_OECGI_REQUEST
but it is designed primarily to manage REST APIs. HTTP_MCP
is a relatively small routine which fits into the SRP philosophy that controllers should be as thin as possible. The basic function of HTTP_MCP
is as follows:
- Call
HTTP_Services
so the HTTP request information is properly parsed so it can be easily retrieved by the rest of the API. - Call
HTTP_Authentication_Services
to validate access to the entry point. - Call the entry point (if allowed).
- Call
HTTP_Services
to get the HTTP response in a proper format that OECGI will accept.
Return the HTTP response to the OECGI.