Compared to direct method calls: bad. Here a short benchmark and the code I wrote for this benchmark (needs PHP 5.3):

define('ITERATIONS', 2000000);
    function doBenchmark($name, Closure $closure){
        $start = microtime(true);
        for ($i=0; $i < ITERATIONS; ++$i) {
            $closure();
        }
        $stop = microtime(true);
        echo "Test $name: " . ($stop - $start) . " seconds";
    }

    class Test{
        public $data = array("view" => "view", "test2" => "test2", "test3" =>"test3");

        public function getView(){
            return $this->data['view'];
        }

        public function __call($name, $arg){
           return $name=="_getView" ? $this->data['view'] : false;
        }

        public function __get($key){
            return array_key_exists($key, $this->data) ? $this->data[$key] : null;
        }
    }

    $t = new Test();
    doBenchmark("Methode Call", function(){
        global $t;
        $v = $t->getView();
    });

    doBenchmark("Direct Access", function(){
        global $t;
        $v = $t->data['view'];
    });

    doBenchmark("Magic Methode (__call)", function(){
        global $t;
        $v = $t->_getView();
    });

    doBenchmark("Magic Methode (__get)", function(){
        global $t;
        $v = $t->view;
    });

So, you get the picure

Don’t use magic methods as a replacement for a regular method if a direct access to a field or variable is possible. Magic methods are the sugar for dynamic created attributes (eg. for database objects) or if you don’t know the method/attribute while writing the code.

Use magic methods only rarely.

The only special magic method you should use often: __autoload It helps to load your needed classes on demand only when they are needed. If you use namespaces, here a short trick to load the name-mangled classes (the $path must of course be changed to your needs):

function __autoload($class) {
    $parts = explode('\\', $class);
    $class = end($parts);
    $path = __DIR__ . "/includes/"); //path for the includes

     require ($path . $class . ".php");
}

Happy coding

Because the free Vmware Player now supports also the creating of virtual machines, it’s
time to make another short benchmark.

Windows 7 Performance Index

Crystal Disk Mark 3.0

Summary

There is no difference for the computing performance. VirtualBox and VMware playing at the same level.
For graphic performance/support VMware wins. VirtualBox 3D support is only rudimentary and does not work for Windows Airo (so the bad performance index for graphics).
The disk/caching performance of VMware is better.

The overall performance of VMware Player is better then VirtualBox.
If you need 3D support eg. for Windows 7 Airo as a guest, VMware is the only solution.
If you need snapshots VirtualBox wins, for such features you need VMware Workstation.

1. Setting error handler

Error handler can be set with the error_page directive. More about this directive you can find here.

Do this in your server block but better use a generic file and include this in every virtual host server block. I use for this a file “vhost” with all such settings.

The handler or html files are placed in a separate folder outside the webs. You can use a folder inside your Nginx settings (I use here for example a “html” folder).

The location block is needed to pass the correct root and file to php fastcgi. In this example I use a file “fastcgi”  with this mostly used lines:

fastcgi_pass   unix:/tmp/fastcgi.socket;
fastcgi_index  index.php;
fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;
include fastcgi_params;

Here the part in the server block (or in your generic vhost file for including):

# error handler, codes can also be combined
error_page 401 /error.php?c=401;
error_page 403 /error.php?c=403;
error_page 404 /error.php?c=404;
error_page 500 /error.php?c=500;
error_page 502 503 504 /error.php?c=50x;

# serve error.php from /etc/nginx/html folder
location =/error.php {
   root /etc/nginx/html;
   include conf/fastcgi;
}

2. PHP file

The error.php file will be called with the URL encoded error-code, so its easy to grab this code in the PHP file from the superglobal $_GET array.

To map this error code to a message string, use a associative array and a function to return the string.

This is the part in the error.php file:

 "Autorisierung erforderlich! - Authorization Required",
    "403" => "Zugriff ist nicht erlaubt! - Access forbidden",
    "404" => "Seite wurde nicht gefunden - Page not found",
    "500" => "Interner Serverfehler - Internal Server Error",
    "50x" => "Seite ist momentan nicht verfügbar. Bitte Anfrage später wiederholen.
-
The page is temporarily unavailable. Try again later.");

// get the error string
function errorString($error) {
    global $_err;

    foreach ($_err as $key => $val) {
        if ($key == $error)
            return $val;
    }

    return "Unknown Error";
}

isset($_GET['c']) or die("Unknown Error");
$error = $_GET['c'];
$str = errorString($error);

?>

Error <?=$error?>: <?=$str?>

You can format the error page as you like. But remember: the web root url will be the actual virtual host! Easiest way: use inline CSS. If this is not your preferred way, place the css file in a virtual host (eg. your default virtual host)

http://mysite.com/phpmyadmin

The location will be append to the root! For a similar behaviour like the Apache configuration, you could use the “alias” directive

My phpmyadmin installation is under /usr/share/phpmyadmin, thats why I use /usr/share as the root.

server{
...
    location /phpmyadmin{
        root    /usr/share;
        index   index.php;
    }

    location ~ \.php$ {
        set $php_root   $document_root;
            if ($request_uri ~* /phpmyadmin) {
                set $php_root /usr/share;
           }

        fastcgi_pass   unix:/tmp/fastcgi.socket;
        fastcgi_index  index.php;
        fastcgi_param  SCRIPT_FILENAME  $php_root$fastcgi_script_name;
        include /etc/nginx/fastcgi_params;
    }
}

A short benchmark of this 4 server with dynamic and static content.
All server provides the same functionality like URL rewriting, password protected folders/files etc. but all have their own way to do that
For shared hosting where the user has no access to the server configuration, Apache with the .htaccess file support is a good choice.

I used the benchmark tool from Apache ab -n 50000 -c 20
php-cgi goes over a Unix socket

Dynamic Content (PHP)

Static content (14785 Bytes HTML file)

More “real live” test with PHP and eAccelerator enabled

Cherokee/NGinx/Lighttp are using the same php-fpm socket

Results

There is a small difference between fast-cgi and php-fpm (alternative implementation of fast-cgi).
You should prefer php-fpm (will be included in PHP 5.4 or you must build it manually from source).

Apache and Cherokee are both excellent for dynamic content.

For static content Lighttp is the fastest server.

There is not _the_ best server but a good combination: Lighttpd or Nginx as a proxy for serving static content, Apache or Cherokee for the dynamic content. Or a another proxy server like Varnish for static content and caching and Apache/Cherokee for serving dynamic content

For a PHP site with only 1 server running: Apache.

For a smaller memory footprint and if .htaccess is not needed: Cherokee (also the only server with a very good graphical admin interface)

Host: Ubuntu64, 4GB RAM, Core2Duo E6600, Samsung HD502IJ
Gast: Windows XP Home, 1GB RAM, 8GB virtual disk
Benchmark Software: SiSoft Sandra Light, HD Tune

Ein kurzer Benchmark der beiden VMs

*) Dual CPU Mode

Resumee

VirtualBox zeigt die bessere Rechenleistung, was sich besonders bei Desktopanwendungen und multimedialastigen Operationen positiv auswirkt.
VMware zeigt die bessere Festplattenperformance, was sich besonders bei Servern positiv bemerkbar macht. Interessant: der Dual CPU Mode in Vmware hat keinen Vorteil zum Single CPU mode).
Man kann sicherlich sagen: VirtualBox für Desktopanwendungen, Vmware für Server, wobei Vmware in der Gesamtperformance der Sieger ist.

Nicht vergessen: Flash != Flex. Flex benutzt zwar Flash Elemente basiert aber auf eigenen Klassen. Wenn Flash und Flex zusammenspielen sollen, benötigen wir eine Schnittstelle.
Ein MovieClip ist ein Anzeigeobjekt in Flash und UIComponent ist ein Anzeigeobjekt in Flex. Wir können aber ein MovieClip in ein UIComponent “verpacken”, so wird das Flex UIComponent ein Container für unseren Flash MovieClip.
Hier nun beide Dateien, zuerst die MXML Datei:

Und die Actionscriptdatei mit der Klasse:

package {
	import mx.core.Application;
	import mx.core.UIComponent;
	import flash.display.MovieClip;

	/*****************************************************************
	 * File: FlexApp.as
	 *****************************************************************/

	public class FlexApp {
		private var _app:Application;

		public function FlexApp(app:Application) {
			_app=app;

			var btn:MovieClip=new BtnStop();
			var flexui:UIComponent=new UIComponent;
			flexui.addChild(btn);
			app.addChild(flexui);
		}

		static public function initApp():FlexApp {
			return new FlexApp(Application(Application.application));
		}

		public function get app():Application {
			return _app;
		}
	}
}

Wie es funktioniert

applicationComplete in der MXML Datei ist der Eventhandler der von der Anwendung aufgerufen wird. Hier setzen wir unseren Handler ein, der eine statische Funktion unser Klasse sein muss damit er auch später aufgerufen werden kann.

initApp() erzeugt unsere Klasse und übergibt das Objekt als Parameter an den Constructor.

Im Constructor erzeugen wir den MovieClip, basierend auf dem von Flash importierten Symbol “BtnStop” (dieses Symbol kommt von einer SWC Bibliothek die vorher mit Flash erzeugt wurde). Es wird dann ein Flex UIComponent erzeugt, wo wir unseren MovieClip als Child hinzufügen. Das UIComponent kann nun zur Flex-Anwendung hinzugefügt werden.

Eclipse schließen und den kompletten Flexbuilder Ordner (Standalone oder Plugin) in diesen dropin Ordner kopieren. Eclipse starten und nun sollte die komplette Flexumgebung zur Verfügung stehen!
Flexbuilder findet man beim Standardinstallationspfad unter C :\Programme\Adobe.

Meine Empfehlung

Für Debuggen, visuelles Design von MXML: FlexBuilder
Für überwiegend Programmierung von Actionscript unter Windows: FlashDevelop.