Marco is getting the point closely. ZF is for sure, very attractive and would make sense for a SaaS solution of OXID, but for a software which is installed by customers at their own server, its not suitable at all.
It's huge and it will decrease perfomance if no caching system is used. In fact, look at magento. They use ZF + their own Varien Framework for Magento. It's well architected, but very very slow. For OXID purposes i would rather suggest the usage of ezComponents, which i've not used yet, but they seem to make more sense than zf to replace single modules of OXID because they can be used independently from the rest of the eZ Components Framework. The only thing it lacks at the moment is a PDF generation library. Best regards, Christopher Simon _______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
