<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>lighty's life: Tag mod_cml</title>
    <link>http://blog.lighttpd.net/articles/tag/mod_cml</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description></description>
    <item>
      <title>mod_cml is dead, long live mod_cml</title>
      <description>&lt;p&gt;Yep, mod_cml will vanish from the distribution of lighttpd 1.5.0. It will get a new name and will get a full blown set of functions to manipulate the execution of a request in lighty.&lt;/p&gt;


	&lt;p&gt;It reason to rename mod_cml is that the focus of this module has changed from the its first implementation. It is not about checking if a request is a cache-hit or not. It is about deciding how to handle a request. Any status code can be returned, any content source will be able to be queried to assemble the content (files, memcache).&lt;/p&gt;


	&lt;p&gt;The main reason is to allow us to change the names like &amp;#8216;trigger_handler&amp;#8217; and &amp;#8216;CACHE_HIT&amp;#8217; to something more appropriate. In the end no big change, but a neccesary one to make the use of this powerful module more obvious. ... Perhaps the new name will be mod_cml &amp;#8230; what would be the new meaning of this abbreviation ? Any suggestions ?&lt;/p&gt;
</description>
      <pubDate>Wed, 02 Aug 2006 23:08:00 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:4fa7b12d-8de1-4b35-a1f7-b653df9353ee</guid>
      <author>jan</author>
      <link>http://blog.lighttpd.net/articles/2006/08/02/mod_cml-is-dead-long-live-mod_cml</link>
      <category>mod_cml</category>
      <trackback:ping>http://blog.lighttpd.net/articles/trackback/1897</trackback:ping>
    </item>
  </channel>
</rss>
