<?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, 23 May 2013 02:06:47 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Padraic Brady's Blog: Zend_Service_Openid Is dead; But It's Reincarnation Is Coming]]></title>
      <guid>http://www.phpdeveloper.org/news/8071</guid>
      <link>http://www.phpdeveloper.org/news/8071</link>
      <description><![CDATA[<p>
In a <a href="http://blog.astrumfutura.com/archives/292-Zend_Service_Openid-Is-dead;-But-Its-Reincarnation-Is-Coming.html">a new post</a> to his blog today, <i>Padraic Brady</i> mentions a component of the Zend Framework that's fallen into the wayside in favor of a Zend-sponsored OpenID component, Zend_Service_Openid. Despite this setback, he still plans on helping with its resurrection, maybe just in a different form.
</p>
<blockquote>
<p>After posting some questions to the mailing list before adding any additional formal proposals, I have learned another OpenID library for the Zend Framework is also in progress within Zend.
</p>
<p>
The upshot of this, given it's a Zend sponsored library, is that I feel like there's little choice but to abandon my own version of a proposal for the framework. So it's status is "withdrawn" at this moment as is Zend_Service_Yadis, being a linked proposal. The library itself is not being abandoned, far from it as it has always been my intention to release it under a New BSD License and that plan is not wavering.
</p>
</blockquote>
<p>
He <a href="http://blog.astrumfutura.com/archives/292-Zend_Service_Openid-Is-dead;-But-Its-Reincarnation-Is-Coming.html">talks about</a> some of the thoughts going through his head of the choice that Zend made and how his library approached the OpenID authentication issues.
</p>]]></description>
      <pubDate>Mon, 18 Jun 2007 14:11:00 -0500</pubDate>
    </item>
  </channel>
</rss>
