<?xml version="1.0" encoding="utf-8"?>
			
			<rss version="2.0">
			<channel>
			<title>Application Generation - Configuration</title>
			<link>http://www.pbell.com/index.cfm</link>
			<description>A series of occasional musings on architecting, securing, optimizing and generating web based applications. By Peter Bell.</description>
			<language>en-us</language>
			<pubDate>Tue, 21 May 2013 18:30:56 -0400</pubDate>
			<lastBuildDate>Thu, 07 Dec 2006 23:59:00 -0400</lastBuildDate>
			<generator>BlogCFC</generator>
			<docs>http://blogs.law.harvard.edu/tech/rss</docs>
			<managingEditor>test@test.com</managingEditor>
			<webMaster>test@test.com</webMaster>
			
			
			
			
			
			<item>
				<title>Configuration: In Language DSLs vs. XML Files</title>
				<link>http://www.pbell.com/index.cfm/2006/12/7/Configuration-In-Language-DSLs-vs-XML-Files</link>
				<description>
				
				I honestly don&apos;t like &lt;a href=&quot;http://www.trampolinesystems.com/weblog/wiring-up-spring-with-jruby/&quot;&gt;this approach&lt;/a&gt;. It is pretty easy to come up with a concise data format for entering data, but I see no particular reason to write it into a programming language. I understand why people dislike XML for large config files, but this seems to me to be a step in the wrong direction . . .
				
				</description>
				
				<category>Configuration</category>
				
				<category>XML</category>
				
				<pubDate>Thu, 07 Dec 2006 23:59:00 -0400</pubDate>
				<guid>http://www.pbell.com/index.cfm/2006/12/7/Configuration-In-Language-DSLs-vs-XML-Files</guid>
				
			</item>
			
		 	
			</channel></rss>
	

