<?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/"
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Keeping changing configuration data</title>
	<atom:link href="http://moshez.wordpress.com/2008/02/07/keeping-changing-configuration-data/feed/" rel="self" type="application/rss+xml" />
	<link>http://moshez.wordpress.com/2008/02/07/keeping-changing-configuration-data/</link>
	<description>Where Moshe Z knows your name</description>
	<lastBuildDate>Fri, 23 Oct 2009 14:51:17 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Building (Virtual) Appliances with Python &#171; Moshe&#8217;z</title>
		<link>http://moshez.wordpress.com/2008/02/07/keeping-changing-configuration-data/#comment-565</link>
		<dc:creator>Building (Virtual) Appliances with Python &#171; Moshe&#8217;z</dc:creator>
		<pubDate>Wed, 01 Apr 2009 14:36:30 +0000</pubDate>
		<guid isPermaLink="false">http://moshez.wordpress.com/?p=65#comment-565</guid>
		<description>[...] You will want to be able to split your code into many processes. These will need to communicate. Since processes tend to die randomly, in the while, you will want the communication to be loosely coupled. The best loosely-coupled communication is shared state. One way to share state is to use an external state storer &#8212; AKA database. Relational or not, and perhaps both, you will want some sort of database. But some state needs to be accessed without calling out to an external process. For that, you will want something like what I already blogged about. [...]</description>
		<content:encoded><![CDATA[<p>[...] You will want to be able to split your code into many processes. These will need to communicate. Since processes tend to die randomly, in the while, you will want the communication to be loosely coupled. The best loosely-coupled communication is shared state. One way to share state is to use an external state storer &#8212; AKA database. Relational or not, and perhaps both, you will want some sort of database. But some state needs to be accessed without calling out to an external process. For that, you will want something like what I already blogged about. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
