<?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: Handling balances in systems</title>
	<atom:link href="http://www.markhneedham.com/blog/2008/08/27/handling-balances-in-systems/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.markhneedham.com/blog/2008/08/27/handling-balances-in-systems/</link>
	<description>Thoughts on Software Development</description>
	<lastBuildDate>Sat, 31 Jul 2010 12:46:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: My Software Development journey so far at Mark Needham</title>
		<link>http://www.markhneedham.com/blog/2008/08/27/handling-balances-in-systems/comment-page-1/#comment-129</link>
		<dc:creator>My Software Development journey so far at Mark Needham</dc:creator>
		<pubDate>Mon, 01 Sep 2008 00:04:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=239#comment-129</guid>
		<description>[...] concurrency was another eye opener for me around how non functional requirements should have an impact on the way that software is designed. It also introduced me to the way that other languages such as [...]</description>
		<content:encoded><![CDATA[<p>[...] concurrency was another eye opener for me around how non functional requirements should have an impact on the way that software is designed. It also introduced me to the way that other languages such as [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randy Nichols</title>
		<link>http://www.markhneedham.com/blog/2008/08/27/handling-balances-in-systems/comment-page-1/#comment-90</link>
		<dc:creator>Randy Nichols</dc:creator>
		<pubDate>Wed, 27 Aug 2008 21:15:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=239#comment-90</guid>
		<description>I found your blog on google and read a few of your other posts.  I just added you to my Google News Reader. Keep up the good work.  Look forward to reading more from you in the future.</description>
		<content:encoded><![CDATA[<p>I found your blog on google and read a few of your other posts.  I just added you to my Google News Reader. Keep up the good work.  Look forward to reading more from you in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Handling balances in systems</title>
		<link>http://www.markhneedham.com/blog/2008/08/27/handling-balances-in-systems/comment-page-1/#comment-89</link>
		<dc:creator>&#187; Handling balances in systems</dc:creator>
		<pubDate>Wed, 27 Aug 2008 21:10:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=239#comment-89</guid>
		<description>[...] The Corner Office &#124; BNET wrote an interesting post today onHere&#8217;s a quick excerpt On one of my previous projects one of the problems that we had to solve was how to handle balances - we were working on a cash service for a financial services company. The main discussion often centres around how often the balance should be updated. From my experience there are two main ways that we can go about this: Real time update after every transaction This is perhaps the most obvious approach and the implementation is fairly simple. After every transaction is executed the appropriate [...]</description>
		<content:encoded><![CDATA[<p>[...] The Corner Office | BNET wrote an interesting post today onHere's a quick excerpt On one of my previous projects one of the problems that we had to solve was how to handle balances &#8211; we were working on a cash service for a financial services company. The main discussion often centres around how often the balance should be updated. From my experience there are two main ways that we can go about this: Real time update after every transaction This is perhaps the most obvious approach and the implementation is fairly simple. After every transaction is executed the appropriate [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
