Until now JSON output has been the only way to obtain all the data flowing through a Pipe. Starting today we've added a second way of getting all the data - serialized PHP Pipe output. [...] It's then up to you on how you want to display or use the Pipe data. The possibilities are endless.

If you haven't messed with Yahoo's Pipes system, you owe to it to yourself to at least go and play with it for a little bit.

Terry Chay made some remarks to my last blog entry about a solution for lazy class loading without using __autoload(). Some of his statements seem like I explained my implementation not good enough leading to wrong interpretations. In this blog entry I'll use some of his statements to take a deeper look into my implementation and show that he has drawed some conclusions which I want to disprove.

He goes back and corrects some of what Terry has said in his response, including showing a more detailed version of him implementation. Be sure to check out the comments for the post, though - Terry comes back and clarifies some of the comments he'd made including the framework talk and changes of perspective having seen the new code snippet/information.

There are already several links to articles (HowTos on creating REST web services) and links to other code examples using the service. Along with this release, they also note that:

...many of their web services now return serialized PHP (developer.yahoo.net/common/phpserial.html). PHP developers will now be able to consume these web services even more easily than before. Yahoo!'s Search, Maps, and Travel REST web services now return serialized PHP by simply adding the "output=php" parameter to any web services request.

The example of this feature has been given in the form of a search for PHP-related podcasts: link here. The resulting output can then be used in a PHP application through the use of the unserialize function. ]]> Wed, 22 Feb 2006 15:17:00 -0600