The second chapter provides a solid grounding on the MVC architecture of ZF. This covers the roles and what part they play in this voodoo magic of making a page render to the browser. The front controller, router, dispatcher, request and response objects are all discussed. This includes an understading of how they fit into the design and ultimately how to leverage getting the best use out of them to fit any custom project requirements.

The remaining part of the book covers the process involved in building a storefront application.

Thus far, this book to me is a good buy with good coverage of design approaches to building the sample application with ZF, together with reasons for those choices.

Can any give reply

All of these syntaxes are useful. Some more than others. a()[$x] is probably more useful than a()(). I could do without the latter, but both have irked me a few times.

(3) is implemented by C#, and Microsoft thought about it a lot. Same re: (4). Almost every language except PHP has a short array grammar.

I’ve implemented IN as:

function EQ()
{
$args = func_get_args();
return Utils::inArray($args[0], array_slice($args, 1));
}

The same could be done for between. Functions sometimes can make up for a lack of an operator. Sure it’s prefix notation, but whatever

function EQ() {
$args = func_get_args();
return in_array($args[0], array_slice($args, 1));
}

if EQ($value, 1, 2, 3) { // do stuff if it’s 1 or 2 or 3 }

Done.

Something I’d really like:

$blog_posts = new blogManager()->getPosts();

This would spare a lot of temporary variables, and avoid a couple of unnecessary Singletons.

This post was mentioned on Twitter by SamHennessy: What or need the #PHP source code used in Zend Server? Find them at http://digs.by/cWx thanks Stat…