<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Wed, 19 Jun 2013 17:27:34 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[PHPMaster.com: Proc_Open: Communicate with the Outside World]]></title>
      <guid>http://www.phpdeveloper.org/news/19693</guid>
      <link>http://www.phpdeveloper.org/news/19693</link>
      <description><![CDATA[<p>
On PHPMaster.com today there's a new tutorial from <i>Timothy Boronczyk</i> about <a href="http://phpmaster.com/proc-open-communicate-with-the-outside-world">using the proc_open function</a> to kick off processes outside of PHP. It can be used to start up and manage (in a limited fashion) external process calls.
</p>
<blockquote>
There are many ways we can interact with other applications from PHP and share data; there's web services, message queuing systems, sockets, temporary files, exec(), etc. Well, today I'd like to show you one approach in particular, proc_open(). The function spawns a new command but with open file pointers which can be used to send and receive data to achieve interprocess communication (IPC).
</blockquote>
<p>
He starts off explaining one of the fundamental concepts behind working with processes - pipes, both anonymous and named. He then moves on to the use of <a href="http://php.net/proc_open">proc_open</a> and the three attributes it takes - command, pipes and references for output. He includes a more practical example showing it in use - a script that converts text with wiki markup into HTML output (via <a href="http://nyctergatis.com/creole/">this tool</a>).
</p>
Link: http://phpmaster.com/proc-open-communicate-with-the-outside-world]]></description>
      <pubDate>Mon, 10 Jun 2013 09:43:01 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[PHPBuilder.com: PHP and Shell Scripting: Using Pipes]]></title>
      <guid>http://www.phpdeveloper.org/news/11943</guid>
      <link>http://www.phpdeveloper.org/news/11943</link>
      <description><![CDATA[<p>
On PHPBuilder.com today there's <a href="http://www.phpbuilder.com/columns/peter_shaw20090211.php3">a new tutorial</a> that takes a deeper look at shell scripting (continuing on from a <a href="http://www.phpbuilder.com/columns/darrell20000319.php3">previous article</a>) with a focus on pipes and their use in simple PHP shell scripts.
</p>
<blockquote>
This article covers some advanced uses of the language and shows some tricks that make PHP an extremely useful language to work with.
Unlike Darrel's article [<a href="http://www.phpbuilder.com/columns/darrell20000319.php3">here</a>] however, this one will also cover the Windows version of PHP as well as the Linux/Unix one.
</blockquote>
<p>
They compare the two operating environments, noting what can and can't be done in each before getting to some of the "neat things" that pipes let you do. They show who to read from stdin (making it easy to pass the results from another command in) and what you can do with the results. Near the end there's also a bit included showing how to do a similar thing on windows (with the help of an <a href=http://www.microsoft.com/windowsserver2003/technologies/management/powershell/download.mspx">external tool</a>).
</p>]]></description>
      <pubDate>Fri, 13 Feb 2009 07:51:52 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Community News: New Yahoo! Pipes PHP serialized output renderer]]></title>
      <guid>http://www.phpdeveloper.org/news/9924</guid>
      <link>http://www.phpdeveloper.org/news/9924</link>
      <description><![CDATA[<p>
As <a href="http://devzone.zend.com/article/3355-Yahoo-Pipes-adds-Serialized-PHP-support">mentioned</a> on the Zend Developer Zone and by <i>John Herren</i>, Yahoo! has added a new feature to its Pipes functionality - <a href="http://jhherren.wordpress.com/2008/04/03/yahoo-pipes-adds-support-for-serialized-php/">serialized PHP results</a>.
</p>
<blockquote>
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.
</blockquote>
<p>
If you haven't messed with <a href="http://pipes.yahoo.com/">Yahoo's Pipes</a> system, you owe to it to yourself to at least go and play with it for a little bit.
</p>]]></description>
      <pubDate>Mon, 07 Apr 2008 12:05:17 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Clay Loveless' Blog: Monitor PHP Extension Releases with Y! Pipes]]></title>
      <guid>http://www.phpdeveloper.org/news/7268</guid>
      <link>http://www.phpdeveloper.org/news/7268</link>
      <description><![CDATA[<p>
Since the recent release of a new tool from Yahoo! - <a href="http://pipes.yahoo.com">Yahoo! Pipes</a> - developers have been working with it and creating their own "pipes" of functionality, already exploring the boundaries of the application. <i>Clay Loveless</i> is one PHP developer that has <a href="http://killersoft.com/randomstrings/2007/02/09/monitor-php-extension-releases-with-y-pipes/">already created</a> his own pipe to monitor feeds from several PHP extensions.
</p>
<blockquote>
The first pipe I've created and published is the <a href="http://pipes.yahoo.com/pipes/HL5Rzu232xG9k5oJuJqdmw/">PHP Extension Monitor</a>. It's an aggregated feed that pulls in release information on several cool extensions that aren't announced in the PECL feed, such as <a href="http://www.hardened-php.net/">Suhosin</a>, <a href="http://trac.lighttpd.net/xcache/">XCache</a> and <a href="http://www.oracle.com/technology/products/berkeley-db/xml/index.html">DBXML</a>.
</blockquote>
<p>
Check out his <a href="http://pipes.yahoo.com/pipes/HL5Rzu232xG9k5oJuJqdmw/">pipe here</a> or you can go create your own by logging in with a Yahoo! ID <a href="http://pipes.yahoo.com/">here</a>.
</p>]]></description>
      <pubDate>Tue, 13 Feb 2007 09:49:00 -0600</pubDate>
    </item>
  </channel>
</rss>
