<?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>Fri, 29 Aug 2008 19:38:48 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Facebook.com: PHPEmbed]]></title>
      <guid>http://www.phpdeveloper.org/news/8886</guid>
      <link>http://www.phpdeveloper.org/news/8886</link>
      <description><![CDATA[<p>
Facebook application developers who already know PHP can be happy about a <a href="http://blog.facebook.com/blog.php?post=6146092130">recent announcement</a> on their blog - the introduction of <a href="http://developers.facebook.com/phpembed/">PHPEmbed library</a> into their setup (as well as a release of it out to the public).
</p>
<blockquote>
In order to make embedding PHP truly simple for all of our developers we developed the PHPEmbed library which is just a more accessible and simplified API built on top of the PHP SAPI. The library is so useful, we decided to share it with the world. Check it out for yourself at <a href="http://developers.facebook.com/phpembed/">http://developers.facebook.com/phpembed/</a>
</blockquote>
<p>
The library (currently in release 20070924) can be grabbed either directly <a href="http://developers.facebook.com/phpembed/download_phpembed.php">from their download link</a> or via the public <a href="http://svn.facebook.com/svnroot/phpembed/">svn repository</a> they've set up. There's also some documentation and help for it in the form of <a href="http://www.facebook.com/group.php?gid=5078262228">a developer's group</a> and the manual (<a href="http://developers.facebook.com/phpembed/phpembed.pdf">PDF</a>/<a href="http://developers.facebook.com/phpembed/docs/index.html">HTML</a>). 
</p>]]></description>
      <pubDate>Tue, 23 Oct 2007 10:27:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Builder.com.au: PHP exploit code plants itself in GIF]]></title>
      <guid>http://www.phpdeveloper.org/news/8107</guid>
      <link>http://www.phpdeveloper.org/news/8107</link>
      <description><![CDATA[<p>
Builder.com.au has a <a href="http://www.builderau.com.au/news/soa/PHP-exploit-code-plants-itself-in-GIF/0,339028227,339278850,00.htm">new article</a> today about the recent image issue - the PHP code embedded inside the GIF - that's come up on several sites.
</p>
<blockquote>
The exploit code slipped through the site's defenses with the aid of a legitimate image at the beginning of the file, <a href="http://isc2.sans.org/diary.html?storyid=2997">according to a blog post</a> on the Sans Institutes's Internet Storm Center. [...] Malicious attackers planted PHP coded exploit script within an image file. PHP is often used as a programming language to create dynamic Web sites.
</blockquote>
<p>
The article reports that, while this exploit hasn't happened much, the occurrences of it's use are growing with victims in a wide range of classifications - from small personal sites out to a certain major image hosting site. This same issue was discussed <a href="http://www.phpdeveloper.org/news/8088">here</a> on the PHPClasses.org website as well.
</p>]]></description>
      <pubDate>Fri, 22 Jun 2007 12:41:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[PHPBuilder.com: Unstoppable Return Receipt Requested Email with PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/7775</guid>
      <link>http://www.phpdeveloper.org/news/7775</link>
      <description><![CDATA[<p>
PHPBuilder.com has a <a href="http://www.phpbuilder.com/columns/equazcion20070502.php3">new article</a> today that shows how to (almost always) know if someone has read an email you've sent or not via a special sort of return receipt request.
</p>
<blockquote>
The problem is that depending on the email client software that your recipient is using, he or she will most likely be given the option to suppress that return-receipt from being sent back to you. This renders the return-receipt system almost completely unreliable as a means of detecting when someone has read your email. If you have access to a web server that's running PHP, you can make your own return-receipt system that is (almost) guaranteed to work.
</blockquote>
<p>
Their method is to <a href="http://www.phpbuilder.com/columns/equazcion20070502.php3">embed an image</a> into the email's content. This image is actually a linked image generated by PHP making it able to grab information about the view status of the email it's included in. 
</p>]]></description>
      <pubDate>Fri, 04 May 2007 10:30:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[The Codist Blog: I Will Never Understand the Appeal Of PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/6873</guid>
      <link>http://www.phpdeveloper.org/news/6873</link>
      <description><![CDATA[<p>
In an <a href="http://codist.biit.com/fiche/thecodist/article/i-will-never-understand-the-appeal-of-php">"interesting" post</a> to The Codist blog, there's one developer's look at PHP and his confession that he'll never quite understand the appeal of the language.
</p>
<blockquote>
How PHP can be so popular is beyond me; the whole sense of encouraging all of your html, code, bindings, javascript, even sql (as in the below example) into a single file is a nightmare.
</blockquote>
<p>
He <a href="http://codist.biit.com/fiche/thecodist/article/i-will-never-understand-the-appeal-of-php">Goes on</a> to talk about his experience with JSP versus PHP and some perspectives on how PHP lacks features he's used to or how other developers he's talked to had similar issues.
</p>
<p>
One thing that concerns me (and apparently several others in the PHP community) is that he keeps talking about procedural PHP code that's an "all in one page" kind of setup. Well, of course this can get messy quickly - that's no way to code anything, much less PHP. Organization means more than just breaking code up into chunks on your page (though it's a very low-level start). Plus, the sample code <a href="http://codist.biit.com/fiche/thecodist/article/i-will-never-understand-the-appeal-of-php">he provides</a> is a joke - a PHP developer with a few weeks of experience could push out something 10x better.
</p>]]></description>
      <pubDate>Tue, 12 Dec 2006 10:04:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[International PHP Magazine: Poll Question: You Did Not Know That]]></title>
      <guid>http://www.phpdeveloper.org/news/6299</guid>
      <link>http://www.phpdeveloper.org/news/6299</link>
      <description><![CDATA[<p>
The International PHP Magazine has conducted a poll on its website over the past week, this time asking "You Did Not Know That...", asking developers which of the true statements about PHP they didn't know about.
</p>
<p>
The options this time were:
<ul>
<li>The trailing '?>' in PHP is Optional
<li>You can embed other programming languages in PHP
<li>Objects can be made to look like arrays by using Standard PHP Library
<li>require is faster than require_once
<li>Anything Less than 5.1.0 is Silly
<li>All
</ul>
There wasn't a whole lot of difference in the results of this poll, but the most all-inclusive of the list was the one selected the most - "All". Following that, was that the trailing closing PHP tag is optional, then a tie for third between the "embed other languages" and "Less than PHP 5.1.0" options.
</p>
<p>
Be sure to cast your vote in their latest poll that asks readers <a href="http://www.php-mag.net/magphpde/magphpde_news/psecom,id,26343,nodeid,5.html">that they're really looking for</a> in their frameworks.
</p>]]></description>
      <pubDate>Mon, 18 Sep 2006 14:16:19 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[SitePoint PHP Blog: __halt_compiler() - how nuts?]]></title>
      <guid>http://www.phpdeveloper.org/news/5363</guid>
      <link>http://www.phpdeveloper.org/news/5363</link>
      <description><![CDATA[<p>
On the SitePoint PHP Blog, <i>Harry Fuecks</i> has <a href="http://www.sitepoint.com/blogs/2006/05/12/__halt_compiler-how-nuts/">a look</a> at the "new(ish) __halt_compiler function" in PHP.
</p>
<quote>
<i>
<p>
<a href="http://simon.incutio.com/">Simon</a> <a href="http://simon.incutio.com/blogmarks/2006/05/10/">blogmarked</a> PHP's new(ish) <a href="http://www.php.net/manual/en/function.halt-compiler.php">__halt_compiler</a> function which, according to the packet: "halts the execution of the compiler. This can be useful to embed data in PHP scripts, like the installation files. Byte position of the data start can be determined by the __COMPILER_HALT_OFFSET__ constant which is defined only if there is a __halt_compiler() presented in the file."
</p>
<p>
It may or may not be an elegant solution (it's certainly relatively simple) but it does have a very valid use case-to allow PHP applications which install themselves from a single script, all related pieces (other PHP scripts, CSS, HTML, images, etc.) being packed at the end of the script in a binary form.
</p>
</i>
</quote>
<p>
<i>Herry</i> also mentions some <a href="http://www.sitepoint.com/blogs/2006/05/12/__halt_compiler-how-nuts/">specific examples</a> of cases that could use it, including <i>Ilia</i>'s <a href="http://fudforum.org/">fudforum</a> software, which makes use of it to perform its installation.
</p>]]></description>
      <pubDate>Sat, 13 May 2006 06:26:55 -0500</pubDate>
    </item>
  </channel>
</rss>
