<?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>Mon, 20 May 2013 10:32:04 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Edin Kadribasic's Blog: PECL4WIN Build Box Dead]]></title>
      <guid>http://www.phpdeveloper.org/news/6706</guid>
      <link>http://www.phpdeveloper.org/news/6706</link>
      <description><![CDATA[<p>
Some <a href="http://edin.dk/archives/19-PECL4WIN-Build-Box-Dead.html">unfortunate news</a> from <i>Edin Kadribasic</i> to be felt particularly by the Windows PHP users out there - the box that hosts the PECL packages for Windows has suffered a bit from a power failure.
</p>
<blockquote>
The power failures are very rare in Denmark, but nonetheless this one managed to take out the build box. The <a href="http://pecl4win.php.net/">website</a> itself is not affected, but there are no updates for the time being.
</blockquote>
<p>
The <a href="http://pecl4win.php.net/">PECL4WIN project</a> hosts a repository of PECL extensions precompiled for the Windows platform. The packaging and distribution system used by PECL is shared with its sister, PEAR.
</p>
<p>
<b>UPDATE</b> (11.15.2006) - The box is <a href="http://edin.dk/archives/20-PECL4WIN-Builder-is-Back.html">back up</a> and working at 100% again (faulty memory was to blame). A new build has already been created.
</p>]]></description>
      <pubDate>Tue, 14 Nov 2006 16:38:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Jamroll.co.uk: Using Lighttpd to Dodge the Digg Effect]]></title>
      <guid>http://www.phpdeveloper.org/news/5591</guid>
      <link>http://www.phpdeveloper.org/news/5591</link>
      <description><![CDATA[<p>
Everyone that knows of the social news site <a href="http://www.digg.com">Digg.com</a> knows the problems that being linked on it can cause. Smaller servers get overloaded and pages can either be very slow loading or completely offline within minutes of being "digged". There's a few out there that have come up with different solutions, but several of them involve mirroring the content somewhere else. In <a href="http://fry.jamroll.co.uk:8080/digg-prevention.html">this proposal</a>, however, they combine the power of Lightttpd and PHP to handle the loads.
</p>
<blockquote>
<p>
We host a wide variety of sites, covering everything from converting your garage into a living space to video game addictions. Because we are such a small operation, being hit by a link from a big site such as Digg would be both a blessing and a curse.
</p>
<p>
In order to place our ads on each page, we use PHP's auto_append_file feature to run our advertisement code. By using PHP's other neato function, auto_prepend_file, I can create a small piece of PHP code to detect when the site is being hit by Digg. In this situation, I have chosen to use <a href="http://lighttpd.net/">Lighttpd</a> to handle the increased loads, because of its proven high performance with large numbers of concurrent connections.
</p>
</blockquote>
<p>
In <a href="http://fry.jamroll.co.uk:8080/digg-prevention.html">his example code</a>, he shows how you can detect when a user is coming from a digg.com page and take them to a cached version of the page they've requested (with the .cache extension).
</p>]]></description>
      <pubDate>Wed, 14 Jun 2006 20:25:34 -0500</pubDate>
    </item>
  </channel>
</rss>
