Brenton Alker-3 wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> This is expected behaviour. Bootstrapping is used to initialize the
> application and is performed before routing-- your archive module may
> even use its bootstrap to add routing rules. So, at this point it is not
> even known which module will be used.
>
> - --
>
> Brenton Alker
> PHP Developer - Brisbane, Australia
>
> http://blog.tekerson.com/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkoxEE4ACgkQ7bkAtAithuvcbACfXIAoobotbpJkWCb8Bb3J3kU0
> TvIAoNSTOgSqcwZiyqapt66q3NhG+F0J
> =K/sD
> -----END PGP SIGNATURE-----
>
>
Oh, that's clearer now for me, thanks for your reply! :-)
So it first will load the "global" bootstrap in the application directory
and then all those at module level, right?
What else, apart from routing rules, is best practice to include in a module
level bootstrap class?
Thanks again.
--
View this message in context:
http://www.nabble.com/ZendApplication-modules-bootstrap-files-tp23979227p23984206.html
Sent from the Zend Framework mailing list archive at Nabble.com.
