Comments on: Zend Framework Bootstrap file class

By: Cron jobs in Zend Framework « DBGLORY 4 YOU

Cron jobs in Zend Framework « DBGLORY 4 YOU — Tue, 07 Jun 2011 17:05:39 +0000

[...] wrote a while ago about my implementation of the bootstrap file and although that doesn’t look to impressive that helped me to build an easy init for the [...]

By: Manufactured Home

Manufactured Home — Fri, 11 Feb 2011 05:06:00 +0000

Great website…and cool article. thanks for the post.

By: Best Registry Cleaner

Best Registry Cleaner — Fri, 17 Dec 2010 14:25:54 +0000

It's easier to remove selected behavior by commenting out the method call, instead of commenting out the whole code-block.

By: registrycleaner

registrycleaner — Fri, 22 Oct 2010 14:28:31 +0000

Great work! Offers registry cleaners for fix registry errors in windows operating system.

By: Best reg cleaner

Best reg cleaner — Mon, 12 Jul 2010 08:47:12 +0000

Oh source code make me dizzyling, but thanks anyway.

By: registry cleaner

registry cleaner — Thu, 14 Jan 2010 18:56:07 +0000

very pleasure to visit this site. nice post. thanks for sharing.

By: Gabi Solomon

Gabi Solomon — Fri, 27 Feb 2009 09:14:32 +0000

@Jani Hartikainen

Yes its true that is doesnt have too much of an advantage over just writing the code, but for me its a little more organized and it has one more advantage. I can write a new prepare method for crons that will not start all of the zend framework ( for example it doesnt need the fron controller ) and i can do it in the same file and not have to do another bootstrapfile.

By: Jani Hartikainen

Jani Hartikainen — Fri, 27 Feb 2009 02:41:11 +0000

I think the idea of separating bootstrap into a class something like yours is good, but the code you show doesn’t seem particularily different from just sticking it outside a class. You could group the code by say delimiting by comments etc. and it would be pretty much the same. Not to mention that the class is just extraneous code that makes it look more complex.

Have you looked at Zym_App? I think that’s a pretty good way to implement this kind of bootstrapping class, which actually ends up doing something else than just wrapping code into methods ( http://www.zym-project.com/docs/reference/zym.app.html )

I guess yours doe have one advantage over the no-class approach: it’s easier to remove selected behavior by commenting out the method call, instead of commenting out the whole code-block.