<?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>Sun, 19 May 2013 19:04:44 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[SmartyCode.com: Serving XHTML in Zend Framework App ]]></title>
      <guid>http://www.phpdeveloper.org/news/12407</guid>
      <link>http://www.phpdeveloper.org/news/12407</link>
      <description><![CDATA[<p>
On the SmartyCode.com site, there was <a href="http://smartycode.com/performance/zend-framework-and-xhtml/">a new article</a> posted recently looking at making the output of your Zend Framework application XHTML compliant.
</p>
<blockquote>
Serving XHTML is often misunderstood by php developers. Frontend engineers simply include the XHTML doctype to their documents, without actually serving document as XHTML. This triggers majority of the browsers to treat such pages as 'tag-soup'. [...] This front controller plugin's code mostly takes concepts from the excellent <a href="http://keystonewebsites.com/articles/mime_type.php">article by Keystone Websites</a>, but implements in Zend Framework environment in an object-oriented way.
</blockquote>
<p>
The code works as a plugin to the controller and runs a few checks on the contents of the data being pushed out (dispatchLoopShutdown) and returns the correct header information (DOCTYPE, language attribute) in the correct XHTML format for the data. When the plugin is registered, all it takes is a call to the "doctype()" method to output the correct information.
</p>]]></description>
      <pubDate>Mon, 27 Apr 2009 07:55:39 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Kae Verens' Blog: Serving files through a script]]></title>
      <guid>http://www.phpdeveloper.org/news/11738</guid>
      <link>http://www.phpdeveloper.org/news/11738</link>
      <description><![CDATA[<p>
<i>Kae Verens</i> has <a href="http://verens.com/archives/2009/01/13/serving-files-through-a-script/">posted a quick tutorial</a> about serving up files by routing them through a "fetch" script, pulling their contents in one side and back out the other.
</p>
<blockquote>
One thing I need to do while building the multi-user version of <a href="http://webme.eu/">webme</a> is to convert it so file references such as /f/photos/an_image.jpg get transparently converted so they serve correctly, even though the actual file may be located somewhere entirely else.
</blockquote>
<p>
There's two steps involved - rewriting the URL request for the types of files you'd like to pull through the script (using some mod_rewrite magic in Apache) and make the script to do the actual work. Source for that is included too. Not only can something like this help you keep things organized but it also allows for extra security if you need to store the files outside of the webserver's document root.
</p>]]></description>
      <pubDate>Wed, 14 Jan 2009 09:37:55 -0600</pubDate>
    </item>
  </channel>
</rss>
