The Zend Framework Community has delivered another feature-rich release of Zend Framework and I'm extremely proud and happy to see the energy and excitement around this project. The ZF team (Wil Sinclair, Matthew Weier O'Phinney, Ralph Schindler, Alexander Veremyev) along with many others in the ZF community and at Zend, have been doing a superb job and have been working very hard to put this release together.

He mentions the Dojo integration, the updates to the SOAP component, updates to make test-driven development simpler and a reminder about ZendCon08 coming soon that will feature several Zend Framework-centric talks.

We couldn't be happier to announce that Zend Framework 1.6 Release Candidate 1 is now available from the Zend Framework download site!

New features include the major Dojo integration, SOAP components and updates to the functionality for unit testing, session handling, pagination, character sets and much more. Check out the full list in the Zend Developer Zone post.

I'm no great expert on the inner workings of these protocols....there are probably secret manuals on SOAP/XmlRpc etc I/we failed to read somewhere. This is just a documentation of what I/we as "newbies" found ...

Resources in the list include things like the SCA SDO module from PECL, some examples of its usage, where it is used, what kind of transport layer the protocol allows and some of the functionality that the Zend Framework allows (including some sample code for a simple server and client).

PHP's next edition, V6, includes new features and syntax improvements that will make it easier to use from an object-oriented standpoint. Other important features, such as Unicode support in many of the core functions, mean that PHP V6 is positioned for better international support and robustness.

New features he mentions include namespace support, improvements to the native Unicode support as well as a few of the things that will be permanently retired like the php.ini settings for magic_quotes and register_globals.

You've tried your hand at building mashups, experimented with a few RESTful Web services, maybe even started your own. Sure, you've got data sharing working. But how do you make your Web applications really talk to each other? In this tutorial, I'll show you how to take your Web applications to the next level with SOAP.

They opt to go with the NuSOAP method to consume another service and create your own simple one. They include a few code examples for either side and a (very) brief look at doing some debugging with what NuSOAP has to offer. One thing to note - if you have PHP5's SOAP extension compiled in and working, NuSOAP will throw an error about redeclaring a class name. This is because of a conflict between the naming of the SOAP extension's methods and NuSOAP.

Despite the fact that you may not have a choice in the matter, upgrading comes with a number of bonus new features that can help you write better code and gain access to new functionality that required a fair amount of hacking in previous version. Here's a quick list of 5 personal favourites.

The feature to make his list are SimpleXML, JSON/SOAP, PDO, the Standard PHP Library and SQLite. Each has their own bonus feature(s) included too for a little extra incentive to check them out.

I spent quite some time looking for info on how to specify the xsi:type for the objects, and I finally came across SoapVar. I created a base class which the SOAP classes extended. A method called pack is responsible for setting xsi:type.

In his example, he creates a BaseClass to work from and builds a createCustomer class on top of it, defining a setCustomer function inside. When the new Person is created, a new Customer is too complete with the correctly formatted type on the object.

The scenario was that when an array with only one object was returned over SOAP the array was discarded and pointed straight to the single object.

Come to find out, this behavior wasn't a bug, it was a feature - the fix is to add another parameter to the initialization of the SoapClient to add the SOAP_SINGLE_ELEMENT_ARRAYS feature.

Web services are the coolest technology I know of that ends up turning everyone off. I don't know about you, but when I go to a lecture on Web services, invariably tons of acronyms come out [...] and then I start to nod off and dream about a land where free Krispy Kreme donuts grow on trees.

He reframes the web services world away from the acronyms and strict standards to more towards using it as a method of communication between apps, letting them engage in some friendly conversation. He uses the rest of the tutorial showing how to create an RSS reader of sorts using dashes of PEAR, XML, C#, XSLT, Ajax and Flex.

I was recently working on a project to expose our trading systems via XmlRpc, Rest and SOAP. It was quite an interesting project, which took two of us three weeks to develop (Amongst other things).

He talks about some of the issues they worked through (like the ZF's "not quite ready" in the web services department) and problems they found with how the web services functionality was implemented in the framework's components. They also came across two strange bugs - one with accepting raw input and the other with a wrong return type from a method call.