<?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 16:05:50 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Yet Another Web Development Blog: Dear PHP, I think it's time we broke up.]]></title>
      <guid>http://www.phpdeveloper.org/news/6935</guid>
      <link>http://www.phpdeveloper.org/news/6935</link>
      <description><![CDATA[<p>
As anyone that's worked with a programming language for a long time knows, you get to know the ins and outs of it pretty well. You get a good feel for how it all works and how feel confident in your skills with it. But what happens if you decide to move on and leave the relationship? Check out <a href="http://blog.rightbrainnetworks.com/2006/12/18/dear-php-i-think-its-time-we-broke-up/">this take</a> on just such a situation from the Yet Another Web Development Blog.
</p>
<blockquote>
We've been together for about five years now. I've had a lot of good times and I've really enjoyed being with you. However, the more we work together, the more concerned I get about our future. I'm sorry, but you don't have the elegance that inspires me to want marry you. I think it's time we broke up.
</blockquote>
<p>
Some of the <a href="http://blog.rightbrainnetworks.com/2006/12/18/dear-php-i-think-its-time-we-broke-up/">reasons given</a> for moving on is PHP's seeming identity crisis, consistency in function names/functionality, and performance issues that were just too much. 
</p>
<p>
Despite being a bit anti-PHP, it's still a well-written piece. <a href="http://blog.rightbrainnetworks.com/2006/12/18/dear-php-i-think-its-time-we-broke-up/">Check it out</a>...
</p>]]></description>
      <pubDate>Tue, 19 Dec 2006 11:56:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Community News: phpMyID (formerly myOpenID) Beta 0.3 Released]]></title>
      <guid>http://www.phpdeveloper.org/news/6926</guid>
      <link>http://www.phpdeveloper.org/news/6926</link>
      <description><![CDATA[<p>
The myOpenID project (which has taken on a new name - <a href="http://siege.org/projects/phpMyID/">phpMyID</a>) has released the latest version of the utility, beta v0.3.
</p>
<blockquote>
phpMyID is a single user (though, if you were so inclined, you could easily turn it into a multi-user setup) IdP, or "Identity Provider" for the OpenID framework. It's a single PHP script with minimal dependancies. You don't need a database, you don't need to make your filesystem writable, you don't need to download any libraries, and you don't need to recompile PHP. Okay, well, you shouldn't need to do any of that.
</blockquote>
<p>
You can get all of the details on the project and the latest downloads from <a href="http://siege.org/projects/phpMyID/">their website</a> including how to install and use the tool.
</p>]]></description>
      <pubDate>Mon, 18 Dec 2006 18:47:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Wez Furlong's Blog: Identity/Authentication and PHP OpenSSL updates in the pipeline]]></title>
      <guid>http://www.phpdeveloper.org/news/6587</guid>
      <link>http://www.phpdeveloper.org/news/6587</link>
      <description><![CDATA[<p>
In his <a href="http://netevil.org/node.php?nid=924">latest post</a>, <i>Wez Furlong</i> shares some of the updates he's made to his blog - specifically when it comes to the external user authentication system he's implemented.
</p>
<blockquote>
Why do I have an external authentication mechanism? I don't want to maintain a user database just for my blog. It's more moving parts and requires things like sending email pings to random email addresses and mechanisms for resetting or retrieving a forgotten password. Not to mention that it's yet another username/password to be remembered by the person doing the commenting.
</blockquote>
<p>
So, instead, he authenticates against the php.net cvs setup for any and all users of his site. He transitions from this over to the main point of the post - his <a href="http://netevil.org/node.php?nid=924">thoughts on authentication</a>, specifically the move towards a more centralized resource to bounce the user's information off of. He mentions <a href="http://www.sixapart.com/typekey/">TypeKey</a> and <a href="http://openid.net/">OpenID</a> as two technologies that are moving in the right direction.
</p>
<p>
Bringing it back to PHP, <i>Wez</i> notes that the PHP support for both of these technologies is very lacking, but he's been working on a patch for the openssl extension that could help that significantly.
</p>]]></description>
      <pubDate>Thu, 26 Oct 2006 13:27:50 -0500</pubDate>
    </item>
  </channel>
</rss>
