Your model should be a 'black box' possible to be used in a different environment than your MVC set. Some Services, Console App even GUI will be possible to be created for your model if you implement your MVC correctly. An easy example - let's say you want to start some logic by cron i.e. from console - there will not be a HTTP request, so your standard request object may not matter anymore. So the key to create a robust, extensible application is implement model as if it is not aware of Controller and View at all. What uses the Request Object is the Controller that passes requests parameters to the Model.
On Tue, Feb 9, 2010 at 11:33 AM, Marko78 <marko.korho...@gmail.com> wrote: > > Hi, > > I have provided my Model base class a straight > access to $_request object just to simplifying my > access to request params from my models. > > Thought it is not forbidden but is it considered > bad design? Is there some aspect I have not thinked > about..? > > br, Marko > -- > View this message in context: > http://n4.nabble.com/Request-in-Models-tp1474066p1474066.html > Sent from the Zend Framework mailing list archive at Nabble.com. > -- Alexander Steshenko | http://lcf.name
