Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In a classic Zend Framework MVC setup, there seems to be access to a generic _request object from within the model/view/controller instance as outlined here:
$this->_request->getPost('variablename');
is this request object somehow available in a non-MVC setup as well?
If yes: how would I initialize and access it?
I would not use the Zend_Controller_Request_* objects outside ZF’s MVC structure (even if possible). You can see by the class name already that it belongs to the controller package and it’s API exposes a number of methods that are completely targeted at being used within ZF’s MVC and these are inherited by all subtypes.
That’s okay when using ZF’s MVC, but for usage outside of that the Request Objects do too much. The idea of a Request object is to encapsulate and maybe decouple the current Request environment from the Superglobals (which ZF doesn’t. It just sits on top). All that extra stuff about modules, controllers and actions shouldn’t be part of it in my opinion. It makes only sense in ZF.
Writing a Request object isn’t difficult, so I’m sure you can easily come up with a more lightweight version. Here is some basic examples:
In the end it’s your choice though.