ZF2 Presentation @PHP Tour 2011 in Lille

Zend Framework 2:
state of the art
by Enrico Zimuel (enrico@zend.com)

Senior Software Engineer
Zend Framework Core Team
Zend Technologies Ltd

PHPTour Lille 2011 – 25 November
http://afup.org/pages/phptourlille2011/
© All rights reserved. Zend Technologies, Inc.

About me

• Software Engineer since 1996
– Assembly x86, C/C++, Java, Perl, PHP
• Enjoying PHP since 1999
• PHP Engineer at Zend since 2008
• ZF Core Team from April 2011
• B.Sc. Computer Science and Economics
Email: enrico@zend.com
Twitter: @ezimuel from University of Pescara (Italy)


Summary

● Overview of ZF2
●
Autoloading
● Dependency Injection
●
Event Manager
●
The new MVC architecture
●
Migrate from ZF1 to ZF2


Overview of ZF2
● Open source framework for PHP, evolution of ZF1
(over 10 million downloads)
● Still in development
– ZF2 beta1 released in October 2011
●
New Betas at least every six weeks (until we're done)
● No more CLA to contribute to ZF2
● We use github (no more SVN)


A new core
● The ZF1 way:
▶ Singletons, Registries, and Hard-Coded
Dependencies
●
The ZF2 approach:
▶ Aspect Oriented Design and Dependency
Injection


Architectural approach

● Methodologies used in the development
– Decoupling (ZendDi)
– Event driven (ZendEventManager)
– Standard interfaces (ZendStdlib)
● Take advantages of PHP 5.3+


Our goal for ZF2

Better consistency
and performance


Autoloading


Autoloading

● No more require_once calls!
●
Multiple approaches:
– ZF1-style include_path autoloader
– Per-namespace/prefix autoloading
– Class-map autoloading


ZF1-Style

require_once 'Zend/Loader/StandardAutoloader.php';

$loader = new ZendLoaderStandardAutoloader(array(
'fallback_autoloader' => true,
));

$loader->register();


ZF2 NS/Prefix

require_once 'Zend/Loader/StandardAutoloader.php';

$loader = new ZendLoaderStandardAutoloader();

$loader->registerNamespace(
'My', __DIR__ . '/../library/My')
->registerPrefix(
'Foo_', __DIR__ . '/../library/Foo');



ZF2 Class-Map

return array(
'MyFooBar' => __DIR__ . '/Foo/Bar.php',
);
.classmap.php

require_once 'Zend/Loader/ClassMapAutoloader.php';

$loader = new ZendLoaderClassMapAutoloader();

$loader->registerAutoloadMap(
__DIR__ . '/../library/.classmap.php');



Classmap generator

● How to generate the .classmap.php ?
We provided a command line tool:
bin/classmap_generator.php
●
Usage is trivial:

$ cd your/library
$ php /path/to/classmap_generator.php -w

● Class-Map will be created in .classmap.php


Performance

●
Class-Maps show a 25% improvement on the ZF1
autoloader when no acceleration is present
▶ and 60-85% improvements when an opcode cache is
in place!

●
Pairing namespaces/prefixes with specific paths
shows >10% gains with no acceleration
▶ and 40% improvements when an opcode cache is in
place!


Dependency
Injection


Dependency injection
●
How to manage dependencies between objects?
●
Dependency injection (Di) is a design pattern whose
purpose is to reduce the coupling between software
components


Di by construct

Without Di With Di (construct)

class Foo { class Foo {
protected $bar; protected $bar;
… …
public function __construct() { public function
$this->bar= new Bar(); __construct(Bar $bar) {
} $this->bar = $bar;
… }
} …
}

Cons: Pros:
Difficult to test Easy to test
No isolation Isolation
Difficult to reuse code Flexible architecture

Di by setter

class Foo {
protected $bar;
…
public function setBar(Bar $bar) {
$this->bar = $bar;
}
…
}


ZendDi
● Supports the 3 different injection patterns:
– Constructor
– Interface
– Setter
●
Implements a Di Container:
– Manage the dependencies using configuration
and annotation
– Provide a compiler to autodiscover classes in a
path and create the class definitions, for
dependencies


Sample definition

$definition = array(
'Foo' => array(
'setBar' => array(
'bar' => array(
'type' => 'Bar',
'required' => true,
),
),
),
);


Using the Di container

use ZendDiDi,
ZendDiConfiguration;

$di = new Di;
$config = new Configuration(array(
'definition' => array('class' => $definition)
));
$config->configure($di);

$foo = $di->get('Foo'); // contains Bar!


Di by annotation

namespace FooBar {
use ZendDiDefinitionAnnotation as Di;

class Baz {
public $bam;
/**
* @DiInject()
*/
public function setBam(Bam $bam){
$this->bam = $bam;
}
}

class Bam {
}
}


Di by annotation (2)

$compiler = new ZendDiDefinitionCompilerDefinition();
$compiler->addDirectory('File path of Baz and Bar');
$compiler->compile();

$definitions = new ZendDiDefinitionList($compiler);
$di = new ZendDiDi($definitions);

$baz = $di->get('FooBarBaz');

More use cases of ZendDi:
https://github.com/ralphschindler/zf2-di-use-cases


Event Manager


The problem

●
How do we introduce logging/debug points in
framework code?
●
How do we allow users to introduce caching
without needing to extend framework code?
●
How do we allow users to introduce validation,
filtering, ACL checks, etc., without needing to
extend framework code?


Event Manager

●
An Event Manager is an object that aggregates
listeners for one or more named events, and
which triggers events.
●
A Listener is a callback that can react to an
event.
●
An Event is an action.


Example

use ZendEventManagerEventManager;

$events = new EventManager();
$events->attach('do', function($e) {
$event = $e->getName();
$params = $e->getParams();
printf(
'Handled event “%s”, with parameters %s',
$event,
json_encode($params)
);
});
$params = array('foo' => 'bar', 'baz' => 'bat');
$events->trigger('do', null, $params);


MVC


Event driven architecture

●
An Application composes a router, a locator, and an
event manager
●
A matching route should return a controller name
●
Controllers are pulled from the locator and
dispatched
● Routing and dispatching are events


Module architecture

“A module is a collection of code and other
files that solves a more specific atomic
problem of the larger business problem.”
(from the ZF2 RFC)


Modules

●
The basic unit in a ZF2 MVC application is
a Module
●
Modules are simply:
▶ A namespace
▶ containing a single classfile, a Module


Example

●
modules/
● Foo/
● Module.php


Module.php

namespace Foo;

class Module { }

● Modules usually also provide:
▶ Autoloading artifacts
▶ Basic configuration


index.php

use ZendModuleManager,
ZendMvcBootstrap,
ZendMvcApplication;

$config = include __DIR__. '/../configs/app.config.php';
$modules = new Manager($config['modules']);

$bootstrap = new Bootstrap($modules);
$app = new Application();
$bootstrap->bootstrap($app);
$app->run()->send();


Controller

namespace FooController;

use ZendMvcControllerActionController;

class HelloController extends ActionController
{
public function worldAction()
{
$query = $this->request->query();
$message = $query->get('message', 'Nobody');
return array('message' => $message);
}
}


Render a view

use ZendEventManagerEventCollection as Events,
ZendEventManagerListenerAggregate;

class ViewListener implements ListenerAggregate
{
/* ... */

public function attach(Events $events)
{
$events->attach('dispatch',
array($this, 'renderView', -100);
$events->attach('dispatch',
array($this, 'renderLayout', -1000);
}

/* ... */
}


Getting dependencies

namespace ContactController;

use ZendMailTransport,
ZendMvcControllerActionController;

class ContactController extends ActionController
{
public function setMailer(Transport $transport)
{
$this->transport = $transport;
}
}


Di configuration
return array('di' => array(
'definition' => array('class' => array(
'ZendMailTransportSmtp' => array(
'__construct' => array(
'host' => array('required' => true, 'type' => false),
'user' => array('required' => true, 'type' => false),
'pass' => array('required' => true, 'type' => false),
),
),
)),
'instance' => array(
'ZendMailTransport' => array('parameters' => array(
'host' => 'some.host.tld',
'user' => 'user',
'pass' => 'pass'
)),
),
);


Source package


Source package

●
http://packages.zendframework.com/
●
Source packages (download + github)
● Pyrus packages:
▶ wget http://packages.zendframework.com/pyrus.phar
▶ pyrus.phar .
▶ pyrus.phar . channeldiscover
packages.zendframework.com
▶ pyrus.phar . install zf2/<zfpackage>
▶ pyrus.phar . install zf2/Zend_<component>


From ZF1 to ZF2


Migrate to ZF2

● Our goal: migrate without rewriting much code!
● Main steps
– Namespace: Zend_Foo => ZendFoo
– Exceptions: an Interface for each components,
no more Zend_Exception
– Autoloading: 3 possible options (one is the same
of ZF1)
▶ MVC: module, event based, dispatchable


ZF1 migration prototype

●
Source code: http://bit.ly/pvc0X1
●
Creates a "Zf1Compat" version of the ZF1
dispatcher as an event listener.
●
The bootstrap largely mimics how ZF1's
Zend_Application bootstrap works.
● The default route utilizes the new ZF2 MVC
routing, but mimics what ZF1 provided.


Helping out

●
http://framework.zend.com/zf2
●
http://github.com/zendframework
●
Bi-weekly IRC meetings (#zf2-meeting on
Freenode IRC)
● #zftalk.2 on Freenode IRC


Thank you!
●
Vote this talk:
▶ http://joind.in/4359

●
Comments and feedbacks:
– enrico@zend.com


ZF2 Presentation @PHP Tour 2011 in Lille

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to ZF2 Presentation @PHP Tour 2011 in Lille

Similar to ZF2 Presentation @PHP Tour 2011 in Lille (20)

More from Zend by Rogue Wave Software

More from Zend by Rogue Wave Software (20)

Recently uploaded

Recently uploaded (20)

ZF2 Presentation @PHP Tour 2011 in Lille