<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.10" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Tech Notes</title>
	<link>http://ken.therickards.com/2006/06/04/tech-notes/</link>
	<description>Ken Rickard's notes about what he's doing</description>
	<pubDate>Wed, 20 Aug 2008 16:40:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.10</generator>

	<item>
		<title>by: Ken Rickard</title>
		<link>http://ken.therickards.com/2006/06/04/tech-notes/#comment-1258</link>
		<pubDate>Wed, 05 Jul 2006 15:43:32 +0000</pubDate>
		<guid>http://ken.therickards.com/2006/06/04/tech-notes/#comment-1258</guid>
					<description>Ha Ha.

For those of you playing along at home.  Every time I say something like "I don't know how we did that." Or, "Real developers worked on that part."  In those cases, I'm probably referring to Kelly. Or Art. Or Tobby.

Especially check out the Search feature on SavannahNow.  Kelly wrote that.</description>
		<content:encoded><![CDATA[<p>Ha Ha.</p>
<p>For those of you playing along at home.  Every time I say something like &#8220;I don&#8217;t know how we did that.&#8221; Or, &#8220;Real developers worked on that part.&#8221;  In those cases, I&#8217;m probably referring to Kelly. Or Art. Or Tobby.</p>
<p>Especially check out the Search feature on SavannahNow.  Kelly wrote that.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Kelly Beck</title>
		<link>http://ken.therickards.com/2006/06/04/tech-notes/#comment-1257</link>
		<pubDate>Wed, 05 Jul 2006 15:26:26 +0000</pubDate>
		<guid>http://ken.therickards.com/2006/06/04/tech-notes/#comment-1257</guid>
					<description>Thanks for the shout out Ken. We could not have done it without you, and I am glad I was able to help :)</description>
		<content:encoded><![CDATA[<p>Thanks for the shout out Ken. We could not have done it without you, and I am glad I was able to help :)
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Ken Rickard</title>
		<link>http://ken.therickards.com/2006/06/04/tech-notes/#comment-1226</link>
		<pubDate>Mon, 03 Jul 2006 15:31:12 +0000</pubDate>
		<guid>http://ken.therickards.com/2006/06/04/tech-notes/#comment-1226</guid>
					<description>We've been testing the filecache as well, but it hadn't been released when I wrote the generator.  

I sent Jeremy some code last week that removes the 'wildcard' barrier from using the file cache, so we're talking.  

The generator does have two additional intended features that filecache doesn't.  Since the files already exist, it allows site editors (there are 4) to preview changes when moving blocks, promoting stories, et. al.

Then when the editor is happy with the changes, they can 'publish' the results.  Workflow that supports a 'staging' server model would be very welcome at the enterprise level.

Second, the generator serves 'static' pages to all users, not just anonymous users.  Since the pages it generates are the most popular on the site, it really made our operations guys happy.

But, that said, I like the fastcache, and we use that as well.</description>
		<content:encoded><![CDATA[<p>We&#8217;ve been testing the filecache as well, but it hadn&#8217;t been released when I wrote the generator.  </p>
<p>I sent Jeremy some code last week that removes the &#8216;wildcard&#8217; barrier from using the file cache, so we&#8217;re talking.  </p>
<p>The generator does have two additional intended features that filecache doesn&#8217;t.  Since the files already exist, it allows site editors (there are 4) to preview changes when moving blocks, promoting stories, et. al.</p>
<p>Then when the editor is happy with the changes, they can &#8216;publish&#8217; the results.  Workflow that supports a &#8217;staging&#8217; server model would be very welcome at the enterprise level.</p>
<p>Second, the generator serves &#8217;static&#8217; pages to all users, not just anonymous users.  Since the pages it generates are the most popular on the site, it really made our operations guys happy.</p>
<p>But, that said, I like the fastcache, and we use that as well.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Dries</title>
		<link>http://ken.therickards.com/2006/06/04/tech-notes/#comment-1222</link>
		<pubDate>Mon, 03 Jul 2006 11:39:30 +0000</pubDate>
		<guid>http://ken.therickards.com/2006/06/04/tech-notes/#comment-1222</guid>
					<description>The generator will be (mostly) deprecated in the next version of Drupal.  CVS HEAD supports multiple cache backends, and the same can be achieved using the 'fastpath file caching' that Jeremy Andrews (CivicSpace) wrote.  That patch was also backported to Drupal 4.7, by the way.  I'd suggest that you check with them, and explore options to collaborate on that file-caching project.</description>
		<content:encoded><![CDATA[<p>The generator will be (mostly) deprecated in the next version of Drupal.  CVS HEAD supports multiple cache backends, and the same can be achieved using the &#8216;fastpath file caching&#8217; that Jeremy Andrews (CivicSpace) wrote.  That patch was also backported to Drupal 4.7, by the way.  I&#8217;d suggest that you check with them, and explore options to collaborate on that file-caching project.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Ken Rickard</title>
		<link>http://ken.therickards.com/2006/06/04/tech-notes/#comment-857</link>
		<pubDate>Mon, 05 Jun 2006 17:45:57 +0000</pubDate>
		<guid>http://ken.therickards.com/2006/06/04/tech-notes/#comment-857</guid>
					<description>Thanks.  I like the generator.module a lot.  It's a funny module, though, since I originally wrote it as a PHP form, using no Drupal functions.

I did that to make sure that the Curl trick would work, and because I wasn't sure which filesystem checks I needed.

It turned out that the file checks I need are all in file.inc (I think).  If more work were going to be done on generator, first it would have to be brought into full Drupal mode.  Then there are some code redundancies to remove.

For a site with multiple editors (this site has at least 6), generator has the added benefit of 'preview' and 'backup.'  Since we generate static pages from dynamic, when an editor moves blocks around, she can preview what the changes might look like before output.

Currently, the module supports one level of restore from backup, though the code could easily support N levels.  Backups are stored in the filesystem, though the database might be better.

- Ken</description>
		<content:encoded><![CDATA[<p>Thanks.  I like the generator.module a lot.  It&#8217;s a funny module, though, since I originally wrote it as a PHP form, using no Drupal functions.</p>
<p>I did that to make sure that the Curl trick would work, and because I wasn&#8217;t sure which filesystem checks I needed.</p>
<p>It turned out that the file checks I need are all in file.inc (I think).  If more work were going to be done on generator, first it would have to be brought into full Drupal mode.  Then there are some code redundancies to remove.</p>
<p>For a site with multiple editors (this site has at least 6), generator has the added benefit of &#8216;preview&#8217; and &#8216;backup.&#8217;  Since we generate static pages from dynamic, when an editor moves blocks around, she can preview what the changes might look like before output.</p>
<p>Currently, the module supports one level of restore from backup, though the code could easily support N levels.  Backups are stored in the filesystem, though the database might be better.</p>
<p>- Ken
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Ken Rickard</title>
		<link>http://ken.therickards.com/2006/06/04/tech-notes/#comment-856</link>
		<pubDate>Mon, 05 Jun 2006 17:40:59 +0000</pubDate>
		<guid>http://ken.therickards.com/2006/06/04/tech-notes/#comment-856</guid>
					<description>Jeff-

Don't get me wrong, VotingAPI is cool, but I don't know that I needed it.  Three main reasons I didn't:

1) I only needed one new Voting app, so an API seemed like overkill. See #2...

2) More modules = more code.

3) Honestly, I wanted to write something from scratch so I could see all the moving parts. Learning the Voting API (which I started) would've shortcut the learning process.

- Ken</description>
		<content:encoded><![CDATA[<p>Jeff-</p>
<p>Don&#8217;t get me wrong, VotingAPI is cool, but I don&#8217;t know that I needed it.  Three main reasons I didn&#8217;t:</p>
<p>1) I only needed one new Voting app, so an API seemed like overkill. See #2&#8230;</p>
<p>2) More modules = more code.</p>
<p>3) Honestly, I wanted to write something from scratch so I could see all the moving parts. Learning the Voting API (which I started) would&#8217;ve shortcut the learning process.</p>
<p>- Ken
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jeff Eaton</title>
		<link>http://ken.therickards.com/2006/06/04/tech-notes/#comment-852</link>
		<pubDate>Mon, 05 Jun 2006 13:36:11 +0000</pubDate>
		<guid>http://ken.therickards.com/2006/06/04/tech-notes/#comment-852</guid>
					<description>Congratulations on the roll out! Sounds like a really great learning experience and a cool site. The generator module in particular sounds great for sites that worry about getting slashdotted, etc.

As the author of VotingAPI, my ears perked up when you mentioned not wanting the overhead of that module. Would you be interested in discussing that? Not to 'convince' you to use it, but rather to figure out ways the API can be improved. I'd love to chat about ways it can be made lighter without sacrificing too much functionality.</description>
		<content:encoded><![CDATA[<p>Congratulations on the roll out! Sounds like a really great learning experience and a cool site. The generator module in particular sounds great for sites that worry about getting slashdotted, etc.</p>
<p>As the author of VotingAPI, my ears perked up when you mentioned not wanting the overhead of that module. Would you be interested in discussing that? Not to &#8216;convince&#8217; you to use it, but rather to figure out ways the API can be improved. I&#8217;d love to chat about ways it can be made lighter without sacrificing too much functionality.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Benjamin Melançon</title>
		<link>http://ken.therickards.com/2006/06/04/tech-notes/#comment-849</link>
		<pubDate>Mon, 05 Jun 2006 11:36:01 +0000</pubDate>
		<guid>http://ken.therickards.com/2006/06/04/tech-notes/#comment-849</guid>
					<description>Hi, I followed your Drupal profile over here.  I was very interested in your user rating module-- now I'm interested in all your work, especially your speed enhancements.  For me the need to scale will come later, so the promise of static page chaching - http://bendiken.net/2006/05/28/static-page-caching-for-drupal - was enough for me to choose Drupal.  But it's great to see you've got improvements working now.  Please do let me know when you contribute the user-rank module.  Thanks!</description>
		<content:encoded><![CDATA[<p>Hi, I followed your Drupal profile over here.  I was very interested in your user rating module&#8211; now I&#8217;m interested in all your work, especially your speed enhancements.  For me the need to scale will come later, so the promise of static page chaching - <a href="http://bendiken.net/2006/05/28/static-page-caching-for-drupal" rel="nofollow">http://bendiken.net/2006/05/28/static-page-caching-for-drupal</a> - was enough for me to choose Drupal.  But it&#8217;s great to see you&#8217;ve got improvements working now.  Please do let me know when you contribute the user-rank module.  Thanks!
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
