<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Wordpress Headaches: Caching and FeedBurner</title>
	<atom:link href="http://blog.uncommons.org/2008/08/01/wordpress-headaches-caching-and-feedburner/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.uncommons.org/2008/08/01/wordpress-headaches-caching-and-feedburner/</link>
	<description>Rants and opinion interspersed with awe-inspiring tales of heoric software engineering endeavours.</description>
	<pubDate>Tue, 06 Jan 2009 21:27:07 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: James</title>
		<link>http://blog.uncommons.org/2008/08/01/wordpress-headaches-caching-and-feedburner/comment-page-1/#comment-2204</link>
		<dc:creator>James</dc:creator>
		<pubDate>Wed, 06 Aug 2008 12:07:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.uncommons.org/?p=103#comment-2204</guid>
		<description>Nice post Dan.

I'm actually glad I came across this post today as I was planning on installing Super-Cache soon and I have feedburner so that wouldn't of been pretty!

Anyway, I think your requirements for the "perfect" blogging platform are pretty much inline with mine. In my opinion, a better approach to Wordpress theming would be similiar to what CushyCMS have implemented. It entails adding classes to elements to signify what content goes where... So:

&lt;pre&gt;
&#60;div class=&#34;post&#34;&#62;
	&#60;h1 class=&#34;post-title&#34;&#62;&#60;/h1&#62;
	&#60;div class=&#34;post-content&#34;&#62;&#60;/div&#62;
&#60;/div&#62;
&lt;/pre&gt;

It would be cool if wordpress could automatically detect the "post" class and loop through the appropriate amount of times putting the right content in the right place. This seems like a much cleaner and fundamentally easier way to apply themes.</description>
		<content:encoded><![CDATA[<p>Nice post Dan.</p>
<p>I&#8217;m actually glad I came across this post today as I was planning on installing Super-Cache soon and I have feedburner so that wouldn&#8217;t of been pretty!</p>
<p>Anyway, I think your requirements for the &#8220;perfect&#8221; blogging platform are pretty much inline with mine. In my opinion, a better approach to Wordpress theming would be similiar to what CushyCMS have implemented. It entails adding classes to elements to signify what content goes where&#8230; So:</p>
<pre>
&lt;div class=&quot;post&quot;&gt;
	&lt;h1 class=&quot;post-title&quot;&gt;&lt;/h1&gt;
	&lt;div class=&quot;post-content&quot;&gt;&lt;/div&gt;
&lt;/div&gt;
</pre>
<p>It would be cool if wordpress could automatically detect the &#8220;post&#8221; class and loop through the appropriate amount of times putting the right content in the right place. This seems like a much cleaner and fundamentally easier way to apply themes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://blog.uncommons.org/2008/08/01/wordpress-headaches-caching-and-feedburner/comment-page-1/#comment-2149</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Sun, 03 Aug 2008 21:54:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.uncommons.org/?p=103#comment-2149</guid>
		<description>Hey Rich, fancy seeing you here :)

Thanks for the pointer to Pebble.  The documentation is a bit sparse but it looks reasonable.  I guess its suitability depends largely on what kind of memory footprint it has.  Java webapps generally aren't very slimline in this respect.  Maybe under Jetty it would be OK?  Especially if I could completely drop Apache and PHP and have Jetty do everything.

It's not clear how themes work with Pebble.  The no database thing is not a show-stopper.  These apps ought to be serving up static files for scalability anyway.

I've been playing around with Django and have managed to write the world's most basic blog engine (seriously spartan).  This is not particularly impressive given that Django gives you half of the functionality for free.  I'm wondering if I can summon up the motivation to actually turn it into something useful.</description>
		<content:encoded><![CDATA[<p>Hey Rich, fancy seeing you here <img src='http://blog.uncommons.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Thanks for the pointer to Pebble.  The documentation is a bit sparse but it looks reasonable.  I guess its suitability depends largely on what kind of memory footprint it has.  Java webapps generally aren&#8217;t very slimline in this respect.  Maybe under Jetty it would be OK?  Especially if I could completely drop Apache and PHP and have Jetty do everything.</p>
<p>It&#8217;s not clear how themes work with Pebble.  The no database thing is not a show-stopper.  These apps ought to be serving up static files for scalability anyway.</p>
<p>I&#8217;ve been playing around with Django and have managed to write the world&#8217;s most basic blog engine (seriously spartan).  This is not particularly impressive given that Django gives you half of the functionality for free.  I&#8217;m wondering if I can summon up the motivation to actually turn it into something useful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich</title>
		<link>http://blog.uncommons.org/2008/08/01/wordpress-headaches-caching-and-feedburner/comment-page-1/#comment-2148</link>
		<dc:creator>Rich</dc:creator>
		<pubDate>Sun, 03 Aug 2008 21:12:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.uncommons.org/?p=103#comment-2148</guid>
		<description>There's Pebble - pebble.sourceforge.net - no idea if it covers everything you want, but it's written in Java and it supports multi-blogs...and it's got a plugin api.

One thing though, it doesn't use *any* database!</description>
		<content:encoded><![CDATA[<p>There&#8217;s Pebble - pebble.sourceforge.net - no idea if it covers everything you want, but it&#8217;s written in Java and it supports multi-blogs&#8230;and it&#8217;s got a plugin api.</p>
<p>One thing though, it doesn&#8217;t use *any* database!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.253 seconds -->
