Re: [fw-mvc] why setting the $bootstrap variable to TRUE in index.php?

Now that you explain it like that, then yes that makes perfect sense.
However, now that this topic has been brought up, I must admit that I am a
much larger fan of keeping the setup outside of the public bootstrap ( as
you changed to within the new quickstart ). I try to abstract my index to
where I can pass in a set of codes, types, and options, and then handle the
setup itself somewhere else down the road. This, I believe, will help with
new developers, projects, and so on.

IE... // cron.php

try {
Bootstrap::getInstance()
->loadObserver('crontab')
->addEvent('crontab')
->dispatch();

} catch (Exception $e) {}

IE... // index.php

try {
Bootstrap::getInstance()->dispatch();
} catch (Exception $e) {}

Maybe it's not exactly in tune with what the discussion is about, but I
think my point is that the setup should be handled as it was changed to...
outside the index.

Matthew Weier O'Phinney-3 wrote:
>
> -- jkush1121 <jonKushner@gmail.com> wrote
> (on Friday, 12 September 2008, 10:11 AM -0700):
>> Don't take my word for final, as this is clearly something which Matthew
>> should respond, but my understanding is that it serves as a preventative
>> measue to ensure that the bootstrap will setup once. Upon turning to
>> false,
>> the setup will bypass. I see what you are saying though, being that it
>> only
>> hits the page one time. It might just be more preventative measures.
>
> It's nothing to do with preventative measures. It's to allow for re-use
> of the bootstrap.php file when testing or scripting, two situations
> where the environment may be setup differently than the standard web
> application.
>
> I'm considering moving this setup to the index.php file prior to calling
> the bootstrap.php file, to allay this confusion.
>
>
>> goriol wrote:
>> >
>> > Hi,
>> >
>> > The new quickstart for ZF 1.6 explains how to create a public index.php
>> > file that will be the only entry point of the application. This file
>> > starts with:
>> >
>> > <?php
>> > // Step 1: Set a flag indicating setup is necessary
>> > $bootstrap = true;
>> > ...
>> >
>> > Then, the boostrap.php is described and an example is given that starts
>> > with:
>> >
>> > <?php
>> > // Step 1: Check to see if the applicaiton environment is already setup
>> > if (isset($bootstrap) && $bootstrap) {
>> > ...
>> >
>> > My question is:
>> > why setting a $bootstrap variable and testing it in the bootstrap file?
>> > As the index.php will be run at every request, the $bootstrap variable
>> > will always be true and the "if" section will always be executed.
>> >
>> > Did I miss something?
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/why-setting-the-%24bootstrap-variable-to-TRUE-in-index.php--tp19458419p19460320.html
>> Sent from the Zend MVC mailing list archive at Nabble.com.
>>
>
> --
> Matthew Weier O'Phinney
> Software Architect | matthew@zend.com
> Zend Framework | http://framework.zend.com/
>
>

--
View this message in context: http://www.nabble.com/why-setting-the-%24bootstrap-variable-to-TRUE-in-index.php--tp19458419p19462290.html
Sent from the Zend MVC mailing list archive at Nabble.com.