<?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>Thu, 20 Jun 2013 06:07:33 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[PEAR Blog: Newly stable packages in PEAR]]></title>
      <guid>http://www.phpdeveloper.org/news/17061</guid>
      <link>http://www.phpdeveloper.org/news/17061</link>
      <description><![CDATA[<p>
The PEAR blog has a recommendation for those that might not have updated their package udage in a while - <a href="http://blog.pear.php.net/2011/10/30/newly-stable-packages-in-pear/">there's been major changes</a> in many packages, but two in particular.
</p>
<blockquote>
We've had 60 releases since July. While most are often minor improvements or bug fixes; a number of packages really stand out. <a href="http://pear.php.net/package/Net_DNS2">Net_DNS2</a>, and <a href="http://pear.php.net/package/HTTP_Request2">HTTP_Request2</a>. Each of these packages represents the second edition of their respective APIs; each having been honed over time to a point of stability.
</blockquote>
<p>
<a href="http://pear.php.net/package/Net_DNS2">Net_DNS2</a> gives you the ability to communicate and resolve host names/domain names inside of a PHP application. <a href="http://pear.php.net/package/HTTP_Request2">HTTP_Request2</a> gives you a simple way to perform HTTP requests.
</p>]]></description>
      <pubDate>Mon, 31 Oct 2011 10:40:03 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Stuart Herbert's Blog: Dealing With PEAR Dependency Quirks]]></title>
      <guid>http://www.phpdeveloper.org/news/16109</guid>
      <link>http://www.phpdeveloper.org/news/16109</link>
      <description><![CDATA[<p>
<i>Stuart Herbert</i> has a new post to his blog today that shares some <a href="http://blog.stuartherbert.com/php/2011/03/28/dealing-with-pear-dependency-quirks/">helpful hints about dependency quirks</a> that can come with using PEAR packages and the PEAR installer.
</p>
<blockquote>
To save myself a bit of effort, I thought it would make sense to make my API client reuse PEAR's existing <a href="http://pear.php.net/package/HTTP_Request2">HTTP_Request2</a> component. No sense in re-inventing the wheel, I thought. But that's where my troubles began. [...] There are a few quirks in the way that the PEAR installer handles version numbers, and you need to know how to deal with them if you're going to re-use PEAR project components in your own apps.
</blockquote>
<p>
He shows how a dependency can be set up for the HTTP_Request2 package as a part of the update to his project. He talks about changes to the project's package.xml file and the trick with version numbering to get the latest. In this case, the latest is a non-stable alpha/beta component and the package.xml file needs some special handling to cooperate there (version, stability, release, api and min/max).
</p>]]></description>
      <pubDate>Mon, 28 Mar 2011 11:09:56 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Zend Developer Zone: Accepting Credit Card Payments with OXID eShop CE and Authorize.Net]]></title>
      <guid>http://www.phpdeveloper.org/news/12768</guid>
      <link>http://www.phpdeveloper.org/news/12768</link>
      <description><![CDATA[<p>
The Zend Developer Zone has <a href="http://devzone.zend.com/article/4780-Accepting-Credit-Card-Payments-with-OXID-eShop-CE-and-Authorize.Net">a new post</a> from <i>Vikram Vaswani</i> about accepting credit card payments through Authorize.net in the <a href="http://www.oxid-esales.com/en/download/open-source-ecommerce-solution-oxid-eshop-community-edition">OXID eShop CE</a> (e-commerce platform).
</p>
<blockquote>
Now, if you're planning to start an online store, it should be pretty clear that accepting electronic payments isn't an option - it's a necessity for you to compete effectively. And that's where this article comes in. Over the next couple of pages, I'll show you how to begin accepting credit card payments for your products using the open source OXID shopping cart and the Authorize.Net payment gateway...with, of course, a little bit of PHP to make things interesting!
</blockquote>
<p>
The glue between the OXID install and Authorize.net is created with the <a href="http://pear.php.net/HTTP_Request2">PEAR HTTP_Request2</a> package. This combined with a little extra PHP code can be installed and used as a component directly inside the application. He gives full code and screenshots to help you get it up and running on your install.
</p>]]></description>
      <pubDate>Fri, 26 Jun 2009 16:48:14 -0500</pubDate>
    </item>
  </channel>
</rss>
