<?xml version="1.0" encoding="utf-8"?>
			
			<rss version="2.0">
			<channel>
			<title>David Harris&apos;s Technology Blog - Transfer</title>
			<link>http://www.harrisfamily.net.nz/devblog/index.cfm</link>
			<description>ColdFusion, Flex and the Universe...</description>
			<language>en-us</language>
			<pubDate>Sat, 25 May 2013 10:01:49 -0500</pubDate>
			<lastBuildDate>Mon, 02 Mar 2009 19:55:00 -0500</lastBuildDate>
			<generator>BlogCFC</generator>
			<docs>http://blogs.law.harvard.edu/tech/rss</docs>
			<managingEditor>harrisfamily.net.nz@gmail.com</managingEditor>
			<webMaster>harrisfamily.net.nz@gmail.com</webMaster>
			
			
			
			
			
			<item>
				<title>Transfer: Something I like about it.</title>
				<link>http://www.harrisfamily.net.nz/devblog/index.cfm/2009/3/2/Transfer-Something-I-like-about-it</link>
				<description>
				
				I&apos;ve been looking in to Mark Mandel&apos;s &lt;a&gt;http://www.transfer-orm.com/,Transfer&lt;/a&gt; bit since he presented to the &lt;a&gt;http://www.cfug.org.nz&lt;/a&gt; end of last year.

One thing (of the many things) I like about it is the XML config file.

Why do I like it?

2 reasons.

1. The fact you can introduce some form of package.class hierarchy to the Database, so flat database&apos;s can be organized better
EG:
&lt;code&gt;
&lt;transfer&gt;
  &lt;objectDefinitions&gt;
    &lt;package name=&quot;mypackage&quot;&gt;
      &lt;object name=&quot;myclass&quot; table=&quot;mytable&quot; &gt;
         &lt;id name=&quot;id&quot; type=&quot;UUID&quot; /&gt;
         &lt;property name=&quot;my property&quot; type=&quot;string&quot; /&gt;
         ...etc...
&lt;/code&gt;
So this means I call my &quot;myclass&quot; like this:
&lt;code&gt;
transfer.getTransfer().new(&quot;mypackage.myclass&quot;);
&lt;/code&gt;

2. The second reason is: I CAN COMMENT THE XML!
Why is this good?
I&apos;m sure we have all returned to database tables with a few to many columns and tried to would out what &quot;status&quot; column and &quot;anotherStatus&quot; column actually relates to in the business logic of the application.
This process involves digging through code and random comments.
With the XML config of transfer, a simple comment on the property can explain it so the next person who needs to work with it knows where look to find out what the class (db table) is for and what purpose the property servers.

Hopefully I&apos;ll find the time to blog some examples on Transfer later.

EG: Event model and decorators
				
				</description>
						
				
				<category>Transfer</category>				
				
				<category>OpenSource</category>				
				
				<category>ColdFusion</category>				
				
				<pubDate>Mon, 02 Mar 2009 19:55:00 -0500</pubDate>
				<guid>http://www.harrisfamily.net.nz/devblog/index.cfm/2009/3/2/Transfer-Something-I-like-about-it</guid>
				
			</item>
			
		 	
			</channel></rss>