The framework archives have been updated.

<?xml is removed from the demos so that those with short_open_tag on in php.ini can run the demo without problem.

The app/demos can now be run wihout placing it in the root directory of a web server.

*Notice: For production mode, it is recommended that you specify the project and framework path in common.conf.php

I am proud to announce that Wendy and David had joined in the team to make DooPHP a greater framework.

Wendy would be improving features for the Model while David is committing new features such as Cache to the framework.

Thank you for your support!

Mean while, the source is up in Google code SVN http://code.google.com/p/doophp/

Due to recent discussions in Kohana framework forum, I decided to test out the latest KohanaPHP which seems to have the same goal as DooPHP.

With KO3 the developers decided to focus on the core, and the core only

This applies to DooPHP too where the core is given priority while extra features like cache, XSS filter, etc. can be added on in the future easily. (Or you can use Zend Framework components, great library!).

Below is the test between DooPHP and Kohana. They are benchmarked with a simple Hello Wolrd and also database ORM.

The result:

Hello World
DooPHP   4765.03 rps
Kohana   1223.48 rps

Database Food SELECT * FROM food
DooPHP   3525.18 rps
Kohana   615.44 rps

*rps = requests per second

Both test are done with persistent connection on without any form of data caching. Configurations are optimized for production mode. The database and data can be downloaded here. It is the same as the database demo.

DooPHP test files download
Kohana test files download
*You will need to download DooPHP framework source to test.

And for those who want to know how the other frameworks are tested, there's a thread in the forum

This benchmark is done on a different machine. Please do not compare this to the one on DooPHP's benchmark page.

Hardware and Environment Details:

• Operating System: Ubuntu Desktop 9.04
• Web Server: Cherokee web server 0.99.16
• PHP: 5.2.9, FastCGI mode, any non-essential extensions are disabled
• CPU: Intel Quad 2 Core 2.5 Ghz
• Main Memory: 2GB DDR2 800Mhz
• Hard Drive: 500GB 7200 RPM SATA HDD

DooPHP can be easily extend to support I18n internationalization and localization for your web applications.

Basically, you just need to extend the DooController and add functions for translation in the template tags.

A demo on I18n is up at the demo section.

Please view it at: http://www.doophp.com/demos

As you can see from the demos, DooPHP does not use any Globals or had any define() used in the code. All configs are done in common.conf.php where variables are defined in assoc array style.

Other than the default configurations which are all in Capitalized characters, you can define your own setting variables. It is recommended that you define them in lowercase as DooPHP might add on new configs in later versions.

$config['salt_key'] = 'jjr7&688e-h3er';
$config['blog_pagesize'] = 12;

#retrieve in your code via:
Doo::conf()->salt_key;
Doo::conf()->blog_pagesize;

This is one good thing about DooPHP as it will not conflict with your application since no define() or globals are used. Not a single one ;)