<?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>Tue, 21 May 2013 15:40:28 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[CIO.com: PHP's Enterprise Strengths and Weaknesses, Take 2]]></title>
      <guid>http://www.phpdeveloper.org/news/9815</guid>
      <link>http://www.phpdeveloper.org/news/9815</link>
      <description><![CDATA[<p>
As is pointed out both by <a href="http://blog.calevans.com/2008/03/17/cio-magazine-take-2/">Cal Evans</a> and the <a href="http://devzone.zend.com/article/3274-CIO-Magazine-Publishes-Second-PHP-Article">Zend Developer Zone</a>, there's been another article posted due to the response from the (now infamous) CIO <a href="http://www.cio.com/article/176250">article</a> - <a href="http://www.cio.com/article/197152/PHP_s_Enterprise_Strengths_and_Weaknesses_Take_">"PHP's Enterprise Strengths and Weaknesses, Take 2"</a> (by Zend's <i>John Coggeshall</i>).
</p>
<blockquote>
So, in the digital toolbox of the developer, where has PHP been designed to work best? And where is it, perhaps, not the best tool for the job? [...] While other languages can surely be used to solve The Web Problem, in this article I explain why PHP is the premier solution for server-side Web scripting.
</blockquote>
<p>
<i>John</i> talks about how PHP was written for the web, how it approaches and handles web requests, the security of the language and some of the major software packages that are being used in PHP development today (like the Zend Framework, PHPUnit and PECL extensions).
</p>]]></description>
      <pubDate>Tue, 18 Mar 2008 11:19:37 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Secunia.com: CodeIgniter Weakness and Directory Traversal Vulnerability]]></title>
      <guid>http://www.phpdeveloper.org/news/8222</guid>
      <link>http://www.phpdeveloper.org/news/8222</link>
      <description><![CDATA[<p>
On the Secunia.com site today, there's <a href="http://secunia.com/advisories/25991/">a new vulnerability posted</a> that users of the CodeIgniter framework should pay attention to - a "weakness and directory traversal vulnerability".
</p>
<blockquote>
Lukasz Pilorz has reported a vulnerability and a weakness in CodeIgniter, which can be exploited by malicious people to disclose sensitive information and conduct cross-site scripting and header injection attacks.
</blockquote>
<p>
There are two problems that lead to this issue - a non-sanitized input parameter and unsanitized data being passed to the xss_clean function. These issues affect <a href="http://codeigniter.com/">CodeIgniter</a> version 1.5.3 and, as of the time of this post, no update has been made in an official release. It is mentioned, however, that the problem has been fixed in the CVS and is waiting for a release.
</p>]]></description>
      <pubDate>Wed, 11 Jul 2007 11:07:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Mike Bernat's Blog: PHP Cookies vs Sessions - The Breakdown]]></title>
      <guid>http://www.phpdeveloper.org/news/6902</guid>
      <link>http://www.phpdeveloper.org/news/6902</link>
      <description><![CDATA[<p>
In a <a href="http://www.mikebernat.com/mikebernat.com/new/?a=article&id=PHP%20Cookies%20vs%20Sessions%20-%20The%20Breakdown">recent post</a> to his blog, <i>Mike Bernat</i> gets down to basics with one of the key pieces of functionality in PHP data persistence - cookies vs. sessions.
</p>
<blockquote>
Knowing the basics of cookies and sessions is essential to any successful PHP programmer. It is useful to store pieces information on the users computer for later use. Things like when they last visited, language of choice, age, etc. Cookies and Sessions are the perfect solution to our needs.
</blockquote>
<p>
He <a href="http://www.mikebernat.com/mikebernat.com/new/?a=article&id=PHP%20Cookies%20vs%20Sessions%20-%20The%20Breakdown">talks about both</a>, including demonstration code to clarify some points and a chart at the end to compare their features, strengths, and weaknesses.
</p>]]></description>
      <pubDate>Thu, 14 Dec 2006 16:58:00 -0600</pubDate>
    </item>
  </channel>
</rss>
