On my current project my team had to develop a portlet interface. Users can load portlets and organize them in multiple tabs with 3 columns per tab. They can reorganize the order of their tabs and move portlets within a tab an also move them to new tabs. Portlets are always placed at the top left when they get added or moved to a tab. Furthermore portlets and tabs can be removed, though the last delete operation can always be undone. All of this essentially required me to devise a plan for how to manage ordered lists inside an RDBMS.

Ok, so as the project moves on from our initial issues with Zend Framework we now come to really appreciate the transparent proxy support that Zend_Http_Client offers. A real time saver for us. But after this short praising I must once again get back to complaining about Zend Framework. We ran into a really hard to find bug in the cookie handling of Zend_Http_Client, which has been filed as a bug back in August 2007 against version 1.0.1 (today we are at 1.5.2). More over this is a bug that other similar packages have gotten over in 2004.

Do they exist? Do they make you money (or in the case of Firebird meaningfully extend your community)? Would you be unhappy if support would be dropped in PHP 5.3, in PHP 6.0? Do you have ressources to prevent this from happening, by taking ownership of the code in question? Are you interested in ensuring the availability of solid support in PDO? While I do not think support will be dropped in PHP 5.3 (well for FrontBaseSQL I have a hard time standing up in defense like I did for the other 3), there is a good chance this will happen in PHP 6.0. Without PDO support your users will be left more or less in the dust. So if you work for one of these vendors, please talk to who ever who can prevent this. If you know someone at these vendors, please contact them or give me the coordinates so that I can do this for you.

Unfortunately my talk proposal for ZendCon 08 was not accepted, which means that I will not have the opportunity to present the vision behind emPHPower at another North American conference this year. Which is a great pity. I was specifically hoping to go to ZendCon 08 because it has a more business oriented focus than other conferences, which would have been a great opportunity to talk to some people about emPHPower that maybe do not read planet-php.org.

Ok, so I have heard the Zend Framework KISS mantra (or "extreme simplicity" as they call it .. or is that something different?) for years. Often enough that I might even be tempted to believe it. Now that I am actually using the Zend Framework on my first project, hitting bugs/limitations in Zend_Feed and therefore looking at the code, I must say I am seeing feature duplication with internal PHP features that does not quite fit in with the KISS principle.