Date: 2016-04-07 11:33
Posted By: Robert Campbell (calguy1000)

for future reference.... any module can do this now with a single layer of
abstraction.

I have (in one module) an action called action.rest.php...  you can register a
route to this action if you want.

There is some code in this action that looks like this:

    $controller = \cge_param::get_string($params,'mymodule_controller');
    $class = "\\controllers\\$controller";
if( !class_exists($class) ) throw new
\ControllerNotFoundException("Controller $controller not found (looking for
class $class)");
    $req_method = strtolower(trim($_SERVER['REQUEST_METHOD']));

// here we're gonna merge in $_REQUEST with $params again just to handle GET
and POST data
    $params = array_merge($_REQUEST,$params);

    $obj = new $class($this);
    $obj->$req_method($params);

This gets the controller class name from a GET/POST parameter named
mymodule_controller, instantiates a new object of that class, gets the request
method... and then calls the appropriate method.   My base controller class
looks like:
abstract class controller
{
    protected $_mod;

    public function __construct(\ImOK $mod)
    {
        $this->_mod = $mod;
    }

    public function __call($method,$args)
    {
        throw new \BadMethodCallException('Method not supported');
    }
}

A derived controller class might look like:

class myController extends \controller
{
    function get($params)
    {
        // handle GET requests to this controller
    }

   function post($params)
   {
       // handle POST requests to this controller.
   }
}


      

Date: 2017-11-20 19:06
Posted By: Robert Campbell (calguy1000)

Controllers can now be classes in CMSMS 2.3
using the invoke method().

And then controller classes can route to different functions for different
request methods.