Results 1 to 24 of 24
Jul 5, 2006, 17:29 #1
- Join Date
- May 2003
- 0 Post(s)
- 0 Thread(s)
Request object? Or use Controller?
I'm building a mvc application. I'd like to make it as simple and independent as possible. I'm wondering how necessary it would be to create a Request object that encapsulates $_GET, $_POST and $_COOKIE?
I'm tempted to simply add methods to the controller base object:
I've also considered just using Controller:aram(), for $_GET, $_POST and $_SERVER['PATH_INFO'], where $_POST would override $_GET... and $_GET would override $_SERVER['PATH_INFO']. Controller::storage() could be for for $_COOKIE.
Is it so wrong to make it as simple as possible? I mean it's MVC, not RMVCR right?