On Friday 05 Nov 2010 16:12:47 Hector Virgen wrote:
> Either way works, but I like your version because I personally believe
> singletons are evil :)
Then why are you suggesting it ;)
That's my idea as well. It's more clear what happens, it's better testable and
you're able to trace the dependen
Hi,
To point out a typo in
http://www.framework.zend.com/manual/en/zend.http.user-agent.html
http://www.framework.zend.com/manual/en/zend.http.user-agent.html
It's
chmod -R o+rwX data/worful/cache
It should be
chmod -R o+rwX data/wurfl/cache
Bye.
Well done folks !
--
View this message in cont
Either way works, but I like your version because I personally believe
singletons are evil :)
Just don't forget to bootstrap the front controller before accessing the
resource, otherwise it will return null.
--
*Hector Virgen*
Sr. Web Developer
http://www.virgentech.com
On Fri, Nov 5, 2010 at
Hi all,
On Friday 05 Nov 2010 14:41:59 Hector Virgen wrote:
> $bootstrap = $application->getBootstrap();
> Zend_Controller_Front::getInstance()->setParam('bootstrap', $bootstrap);
While most tutorials use the Singleton pattern of the frontController, I see
myself using the bootstrap more often:
Brilliant, worked like a charm!
Thanks Hector :)
Regards,
Saša Stamenković
On Fri, Nov 5, 2010 at 2:41 PM, Hector Virgen wrote:
> I believe that param is added when the application is run(). Since you're
> not calling run(), you'll need to add that param manually:
>
> $bootstrap = $applicatio
I believe that param is added when the application is run(). Since you're
not calling run(), you'll need to add that param manually:
$bootstrap = $application->getBootstrap();
Zend_Controller_Front::getInstance()->setParam('bootstrap', $bootstrap);
--
Hector Virgen
Sent from my Droid X
On Nov 4,
