<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-US">

    <title>LightPress</title>
    <subtitle>A fast, template-based frontend for WordPress</subtitle>
    <updated>2007-03-20T15:22:14+00:00</updated>
    <id>http://lightpress.org/</id>
    <link rel="alternate" type="text/html" hreflang="en-US" href="http://lightpress.org" />
    <link rel="self" type="application/atom+xml" href="http://lightpress.org/atom.xml" />
    <rights type="html"><![CDATA[&lt;br /&gt;&amp;copy;2004-2006 L. Magnocavallo, J. Lavigne. Header image &amp;copy; &lt;a href=\&quot;http://flickr.com/photos/vanhap/\&quot;&gt;vanhap&lt;/a&gt;.]]></rights>
    <generator uri="http://lightpress.org" version="2.0.0">LightPress 2.0.0</generator>

    
    <entry>
        <title type="html">Akismet Support</title>
        <link rel="alternate" type="text/html" href="http://lightpress.org/post/akismet-support" />
        <id>http://lightpress.org/post/akismet-support/</id>
        <author>
            <name>ludo</name>
        </author>
        <published>2006-06-07T15:29:55+00:00</published>
        <updated>2006-06-07T15:29:55+00:00</updated>
        <content type="html" xml:lang="en-US" xml:base="http://lightpress.org/post/akismet-support"><![CDATA[<p>In the <a href="http://lightpress.org/downloads/nightlies/">latest nightly build</a>, together with <a href="http://lightpress.org/lightpress/timeline">lots of fixes and improvements</a>. Getting ready for a 2.0 release.</p>]]></content>
    </entry>
    
    <entry>
        <title type="html">Lighttpd Support</title>
        <link rel="alternate" type="text/html" href="http://lightpress.org/post/lighttpd-support" />
        <id>http://lightpress.org/post/lighttpd-support/</id>
        <author>
            <name>ludo</name>
        </author>
        <published>2005-10-24T14:54:23+00:00</published>
        <updated>2005-10-24T14:54:23+00:00</updated>
        <content type="html" xml:lang="en-US" xml:base="http://lightpress.org/post/lighttpd-support"><![CDATA[<p>I have just committed preliminary support for <a href="http://www.lighttpd.net/">Lighttpd</a> rewrite rules in LightPress. If you feel adventurous, you can download our <a href="http://lightpress.org/downloads/lightpress-1.2-dev.tar.gz">development package</a> and let us know of anything that needs fixing. I am not a Lighttpd expert, so any input is welcome.</p>]]></content>
    </entry>
    
    <entry>
        <title type="html">WP pages patch</title>
        <link rel="alternate" type="text/html" href="http://lightpress.org/post/wp-pages-patch" />
        <id>http://lightpress.org/post/wp-pages-patch/</id>
        <author>
            <name>ludo</name>
        </author>
        <published>2005-09-05T14:33:36+00:00</published>
        <updated>2005-09-05T14:33:36+00:00</updated>
        <content type="html" xml:lang="en-US" xml:base="http://lightpress.org/post/wp-pages-patch"><![CDATA[<p>Fresh from two weeks of holidays in beautiful <a href="http://www.discoverlanzarote.com/famara.asp">Lanzarote</a>, I tried to tackle <a href="http://lightpress.org/post/wp-pages">the WP pages problem</a> I outlined in my previous post. The result is <a href="http://lightpress.org/lightpress/changeset/129?format=diff">a 150 lines patch</a> for</p>
<code>
wp-admin/edit-pages.php</code>
<p>, which brings rendering time down from 18 seconds to less than 1 second in my test blog with 200 pages.  The patch is also available as <a href="http://lightpress.org/lightpress/file/wp-patches/trunk/edit-pages.php">a drop-in php file</a>, but remember to backup the original WP file in case you run into problems later.</p>]]></content>
    </entry>
    
    <entry>
        <title type="html">Poor Man&#039;s Benchmark</title>
        <link rel="alternate" type="text/html" href="http://lightpress.org/post/poor-mans-benchmark" />
        <id>http://lightpress.orgpost/poor-mans-benchmark</id>
        <author>
            <name>ludo</name>
        </author>
        <published>2005-07-16T15:12:34+00:00</published>
        <updated>2005-07-16T15:12:34+00:00</updated>
        <content type="html" xml:lang="en-US" xml:base="http://lightpress.org/post/poor-mans-benchmark"><![CDATA[<p>Just did a series of poor man's benchmarks against beta3, using Apache Benchmark with no concurrent requests (ab -n 100):</p>
<table border="0" cellpadding="3" cellspacing="1">

<tr>
<td>
<p>vanilla WP 1.5.1</p>
</td>
<td align="right">
<p>3.90 req/s</p>
</td>

</tr>
<tr>
<td>
<p>LP 1.1.0beta3</p>
</td>
<td align="right">
<p>11.90 req/s</p>
</td>

</tr>
<tr>
<td>
<p>LP 1.1.0beta3 with cache</p>
</td>
<td align="right">
<p>119.90 req/s</p>
</td>

</tr>
</table>
<p>I am too lazy to install wp-cache, but <a href="http://www.sencer.de/article/1198/weblog-software-benchmark-ii">using Sencer's benchmark to do the math</a> we should be about 50% faster than wp-cache. I will try to find the time to install wp-cache on this machine and have some real numbers, but not before we release beta3.</p>]]></content>
    </entry>
    
    <entry>
        <title type="html">Development Status/beta3</title>
        <link rel="alternate" type="text/html" href="http://lightpress.org/post/development-statusbeta3" />
        <id>http://lightpress.orgpost/development-statusbeta3</id>
        <author>
            <name>ludo</name>
        </author>
        <published>2005-07-15T18:09:02+00:00</published>
        <updated>2005-07-15T18:09:02+00:00</updated>
        <content type="html" xml:lang="en-US" xml:base="http://lightpress.org/post/development-statusbeta3"><![CDATA[<p>Beta 3 is almost ready to be released, with two new important features: a regression testing engine that Jerome is developing which will allow us to thouroughly test new releases, and a new built-in caching system.</p>
<p>We already had a few caching objects lying around, but were missing an appropriate hook where to plug the cache. We now have the hook, and a sketch of the supporting WP plugin to configure the cache engine. The results are not so bad, as the speed with caching enabled is 8x the speed without caching, <a href="http://www.sencer.de/article/1198/weblog-software-benchmark-ii">which should make us faster than wp-cache</a> (did you have any doubt?).</p>
<p>What spurred us into action is <a href="http://comox.textdrive.com/pipermail/wp-hackers/2005-July/thread.html">an interesting thread on the wp-hackers mailing list</a> (take the time to read <a href="http://weblog.textdrive.com/">Jason Hoffman</a>'s messages as they are worth it), and particularly <a href="http://comox.textdrive.com/pipermail/wp-hackers/2005-July/001961.html">a phrase by Matt</a> which we hope won't hold true for long. :)</p>]]></content>
    </entry>
    
    <entry>
        <title type="html">Paths and Escaping</title>
        <link rel="alternate" type="text/html" href="http://lightpress.org/post/paths-and-escaping" />
        <id>http://lightpress.orgpost/paths-and-escaping</id>
        <author>
            <name>jerome</name>
        </author>
        <published>2005-07-09T06:51:58+00:00</published>
        <updated>2005-07-09T06:51:58+00:00</updated>
        <content type="html" xml:lang="en-US" xml:base="http://lightpress.org/post/paths-and-escaping"><![CDATA[<p><strong>Just a short announcement about a few bugs in <a href="/post/110-beta1" title="LightPress 1.1.0-beta1">the latest beta</a>. </strong> Most are minor and are either usability-related or affect how the plugin synchronizes WordPress and LightPress options.  But there's a major one that will prevent Windows users from enjoying the new backend interface.  It has to do with paths and escaping -- although that may sound like the basis for a great movie, trust me, it's not so exciting.</p>
<p>As the token Windows user on the team, it's normally my job to find these things and fix them.  I apologize for letting you all down.  If you really want to try the latest beta, why not try another OS at the same time?  Or you could wait a few days until we release the next beta.  <em>[Or you can grab the wp-plugin/ folder from <a href="http://sourceforge.net/cvs/?group_id=136147">our anonymous CVS</a> --ludo.]</em> Your choice.</p>]]></content>
    </entry>
    
    <entry>
        <title type="html">A new beta coming soon</title>
        <link rel="alternate" type="text/html" href="http://lightpress.org/post/a-new-beta-coming-soon" />
        <id>http://lightpress.org/post/a-new-beta-coming-soon</id>
        <author>
            <name>ludo</name>
        </author>
        <published>2005-07-05T13:20:35+00:00</published>
        <updated>2005-07-05T13:20:35+00:00</updated>
        <content type="html" xml:lang="en-US" xml:base="http://lightpress.org/post/a-new-beta-coming-soon"><![CDATA[<p>We have <strong>not</strong> disappeared. We are working on 1.1.0 beta 1 which will hopefully be released in the next few days, and will feature quite a few improvements and bug fixes over the latest 1.1.0 alpha release:</p>
<ul>

<li>
<p>seamless integration with WP's permalink options and automatic .htaccess generation</p>
</li>

<li>
<p>support for nested pages (static posts in LP-speak) and categories</p>
</li>

<li>
<p>no need to touch the filesystem (move/rename WP files, copy LP files, etc.)</p>
</li>

</ul>
<p>There are lots of other exciting new features scheduled after beta 1. Stay tuned...</p>]]></content>
    </entry>
    
    <entry>
        <title type="html">Progressing</title>
        <link rel="alternate" type="text/html" href="http://lightpress.org/post/progressing-2" />
        <id>http://lightpress.org/post/progressing-2</id>
        <author>
            <name>ludo</name>
        </author>
        <published>2005-06-14T16:43:05+00:00</published>
        <updated>2005-06-14T16:43:05+00:00</updated>
        <content type="html" xml:lang="en-US" xml:base="http://lightpress.org/post/progressing-2"><![CDATA[<p><a href="http://lightpress.org/uploads/lp_console.jpg"><img src="http://lightpress.org/uploads/lp_console_small.jpg" style="margin-right: 3px;" align="left" border="0" width="240" height="183" alt="" /></a>I'm progressing with the WP plugin for WordPress, which is the main thing missing before releasing 1.1.0-alpha1. It will alow users to set options, and activate/deactivate/configure plugins.</p>
<p>It's a lot of (boring) work, but seeing the LP console taking shape and knowing users will have a graphical install/configuration tool integrated with WP is pretty exciting. Stay tuned. :)</p>]]></content>
    </entry>
    
    <entry>
        <title type="html">Development Status</title>
        <link rel="alternate" type="text/html" href="http://lightpress.org/post/development-status" />
        <id>http://lightpress.org/post/development-status</id>
        <author>
            <name>ludo</name>
        </author>
        <published>2005-06-11T08:40:03+00:00</published>
        <updated>2005-06-11T08:40:03+00:00</updated>
        <content type="html" xml:lang="en-US" xml:base="http://lightpress.org/post/development-status"><![CDATA[<p>A few quick notes on the current status of development.</p>
<p>The mock-up for the "split" architecture involving a sort of mvc layout for Frontend did not go too well: the code is much more complex and, though more flexible in some situations, it also seems a bit slower so iI have abandoned it for the time being.</p>
<p>In the last couple of days I have concentrated on speed in the 1.0.0 maintenance branch:</p>
<ul>

<li>
<p>removed all PEAR dependencies and switched all classes to the PHP error system</p>
</li>

<li>
<p>refactored Frontend to allow context-dependent queries before we fetch posts</p>
</li>

<li>
<p>added a getLastModified() method to Frontend which checks the last modification date for the context posts and optionally comments</p>
</li>

<li>
<p>added two caching classes</p>
</li>

</ul>
<p>The Cache classes are a very clean db-based one which I like a lot  and a filesystem-based one. Both classes give a 7x performance boost checking LastModified(), to do better we have to integrate with the WP backend like the excellent <a href="http://mnm.uib.es/gallir/wp-cache-2/">wp-cache</a> does. The fs-class still needs work, and the integration with Frontend is sub-optimal. Will work a bit more on that in the next few days, if there's any interest. The new code can be found <a href="http://cvs.sourceforge.net/viewcvs.py/lightpress/wp-frontend/classes/?only_with_tag=Frontend_1-0-maintenance">in CVS</a>.</p>
]]></content>
    </entry>
    
    <entry>
        <title type="html">PHP, HTTP/1.1 dates and Conditional Get</title>
        <link rel="alternate" type="text/html" href="http://lightpress.org/post/php-http11-dates-and-conditional-get" />
        <id>http://lightpress.org/post/php-http11-dates-and-conditional-get</id>
        <author>
            <name>ludo</name>
        </author>
        <published>2005-06-08T15:03:47+00:00</published>
        <updated>2005-06-08T15:03:47+00:00</updated>
        <content type="html" xml:lang="en-US" xml:base="http://lightpress.org/post/php-http11-dates-and-conditional-get"><![CDATA[<p>One of the benefits we might get from the <a href="http://lightpress.org/post/is-frontend-too-big#249">new architecture I'm testing</a> is a much more integrated and simpler feed management, so while adapting the current code to the new class layout I took the occasion to revise or support for <a href="http://fishbowl.pastiche.org/archives/001132.html">Conditional Get</a>.</p>
<p>I had already adapted <a href="http://simon.incutio.com/archive/2003/04/23/conditionalGet">Simon Willison's code</a> to work around a <a href="http://bugs.php.net/bug.php?id=31842">bug in PHP's</p>
<code>
date</code>
<p>formats</a> (fixed in 4.3.11), but the code was a bit too complex for my tastes, and re-reading the relevant parts of the <a href="http://www.faqs.org/rfcs/rfc2616.html" title="RFC2616#3.3.1">HTTP/1.1 specification</a>, I noticed that full compliance requires supporting three different date formats, all in GMT:</p>
<blockquote>
<p>Sun, 06 Nov 1994 08:49:37 GMT ; RFC 822, updated by RFC 1123<br />
<br /><br />
Sunday, 06-Nov-94 08:49:37 GMT ; RFC 850, obsoleted by RFC 1036<br />
<br /><br />
Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format</p>
<p>All HTTP date/time stamps MUST be represented in Greenwich Mean Time (GMT), without exception.</p>
<p>HTTP/1.1 clients and servers that parse the date value MUST accept all three formats (for compatibility with HTTP/1.0), though they MUST only generate the RFC 1123 format for representing HTTP-date values in header fields.</p>
</blockquote>
<p> <a href="http://lightpress.org/post/php-http11-dates-and-conditional-get">continued</a>]]></content>
    </entry>
    
</feed>

