[zeta-dev] proposal: an http (webservice) client component
Iirc there was alreday in the past some such request in the past, but it never came to pass. In this era of mashups and webservices, having something more advanced than a plain curl handle might be a good thingh. I am offering the source code of my current library, implemented as part of the ggwebservices extension of ezpublish - you can find it here: http://svn.projects.ez.no/ggwebservices/trunk/extension/ggwebservices/ - it does not (yet) follow the zetac coding standards, but it is not too far away from them imho - it follows the original ezpublish soap api - it implements both client and server side; client side can be scrapped or rewritten based on zc-mvc - it supports a wide range of protocols: soap, xmlrpc, jsonrpc, rest - it supports curl and no-curl installations Any comments are of course welcome bye Gaetano
Re: [zeta-dev] The Piwi Framework
On Fri, Nov 4, 2011 at 11:35 AM, Fabrice PICCINALI wrote: > And what about pear ? > pear install zeta > It is well-know, easy to use and you can have your custom depot. I always have problems with pear and would have no problem if it would go over Styx - so sooner, so better. > > > On 04/11/2011 11:02, Christian Grobmeier wrote: >> >> On Fri, Nov 4, 2011 at 10:33 AM, Henri Bergius >> wrote: >>> >>> On Thu, Nov 3, 2011 at 3:48 PM, Christian Grobmeier >>> wrote: But it seems, there is less interest. Don't know whats wrong, but it seems the PHP world is overloaded with frameworks. It seems, even a high quality framework as Zeta does suffer from this fact. >>> >>> In general, PHP has too many frameworks, and too few reusable >>> libraries. I think for AZC it would be better to position itself as a >>> managed collection of high-quality libraries than to try and position >>> as a framework. After all, Zeta components can already be used outside >>> of Zeta-managed framework code (for example, both Midgard MVC and >>> Symfony2 have integrations with the Workflows component). >> >> +1 >> >> A similar project is commons.apache.org. It works very well. >> >>> Which brings me to another point I wanted to take up. How about >>> packaging and distributing AZC through the new Composer system? That >>> would make the Zeta components quite accessible and easy to depend on: >>> http://bergie.iki.fi/blog/composer_solves_the_php_code-sharing_problem/ >> >> Sounds very interesting. Will follow this project >> >> Cheers >> Christian >> >> Christian >>> >>> /Henri >>> >>> -- >>> Henri Bergius >>> Motorcycle Adventures and Free Software >>> http://bergie.iki.fi/ >>> >>> Jabber: henri.berg...@gmail.com >>> Microblogs: @bergie >>> >> > -- http://www.grobmeier.de
Re: [zeta-dev] The Piwi Framework
On Fri, Nov 4, 2011 at 12:35 PM, Fabrice PICCINALI wrote: > And what about pear ? > > pear install zeta > > It is well-know, easy to use and you can have your custom depot. PEAR is ok for end users, but quite a pain for developers. It also assumes a global installation of packages, while Composer installs everything into your project. Way easier when you have multiple projects on a machine. Composer also generates an autoloader for you. -- Henri Bergius Motorcycle Adventures and Free Software http://bergie.iki.fi/ Jabber: henri.berg...@gmail.com Microblogs: @bergie
Re: [zeta-dev] The Piwi Framework
And what about pear ? pear install zeta It is well-know, easy to use and you can have your custom depot. On 04/11/2011 11:02, Christian Grobmeier wrote: On Fri, Nov 4, 2011 at 10:33 AM, Henri Bergius wrote: On Thu, Nov 3, 2011 at 3:48 PM, Christian Grobmeier wrote: But it seems, there is less interest. Don't know whats wrong, but it seems the PHP world is overloaded with frameworks. It seems, even a high quality framework as Zeta does suffer from this fact. In general, PHP has too many frameworks, and too few reusable libraries. I think for AZC it would be better to position itself as a managed collection of high-quality libraries than to try and position as a framework. After all, Zeta components can already be used outside of Zeta-managed framework code (for example, both Midgard MVC and Symfony2 have integrations with the Workflows component). +1 A similar project is commons.apache.org. It works very well. Which brings me to another point I wanted to take up. How about packaging and distributing AZC through the new Composer system? That would make the Zeta components quite accessible and easy to depend on: http://bergie.iki.fi/blog/composer_solves_the_php_code-sharing_problem/ Sounds very interesting. Will follow this project Cheers Christian Christian /Henri -- Henri Bergius Motorcycle Adventures and Free Software http://bergie.iki.fi/ Jabber: henri.berg...@gmail.com Microblogs: @bergie
Re: [zeta-dev] The Piwi Framework
On Fri, Nov 4, 2011 at 10:33 AM, Henri Bergius wrote: > On Thu, Nov 3, 2011 at 3:48 PM, Christian Grobmeier > wrote: >> But it seems, there is less interest. Don't know whats wrong, but it >> seems the PHP world is overloaded with frameworks. It seems, even a >> high quality framework as Zeta does suffer from this fact. > > In general, PHP has too many frameworks, and too few reusable > libraries. I think for AZC it would be better to position itself as a > managed collection of high-quality libraries than to try and position > as a framework. After all, Zeta components can already be used outside > of Zeta-managed framework code (for example, both Midgard MVC and > Symfony2 have integrations with the Workflows component). +1 A similar project is commons.apache.org. It works very well. > Which brings me to another point I wanted to take up. How about > packaging and distributing AZC through the new Composer system? That > would make the Zeta components quite accessible and easy to depend on: > http://bergie.iki.fi/blog/composer_solves_the_php_code-sharing_problem/ Sounds very interesting. Will follow this project Cheers Christian > >> Christian > > /Henri > > -- > Henri Bergius > Motorcycle Adventures and Free Software > http://bergie.iki.fi/ > > Jabber: henri.berg...@gmail.com > Microblogs: @bergie > -- http://www.grobmeier.de
Re: [zeta-dev] The Piwi Framework
On Thu, Nov 3, 2011 at 3:48 PM, Christian Grobmeier wrote: > But it seems, there is less interest. Don't know whats wrong, but it > seems the PHP world is overloaded with frameworks. It seems, even a > high quality framework as Zeta does suffer from this fact. In general, PHP has too many frameworks, and too few reusable libraries. I think for AZC it would be better to position itself as a managed collection of high-quality libraries than to try and position as a framework. After all, Zeta components can already be used outside of Zeta-managed framework code (for example, both Midgard MVC and Symfony2 have integrations with the Workflows component). Which brings me to another point I wanted to take up. How about packaging and distributing AZC through the new Composer system? That would make the Zeta components quite accessible and easy to depend on: http://bergie.iki.fi/blog/composer_solves_the_php_code-sharing_problem/ > Christian /Henri -- Henri Bergius Motorcycle Adventures and Free Software http://bergie.iki.fi/ Jabber: henri.berg...@gmail.com Microblogs: @bergie
