<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" media="screen" href="/styles/xslt/rss.xslt"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:c9="http://channel9.msdn.com">
<channel>
	<title>Comment Feed for Channel 9 - ARCast.TV - Brian Noyes on Selecting the Correct Client Technology</title>
	<atom:link rel="self" type="application/rss+xml" href="http://channel9.msdn.com/Shows/ARCast.TV/ARCastTV-Brian-Noyes-on-Selecting-the-Correct-Client-Technology/RSS"></atom:link>
	<image>
		<url>http://ecn.channel9.msdn.com/o9/previewImages/100/456095_100x75.jpg</url>
		<title>Channel 9 - ARCast.TV - Brian Noyes on Selecting the Correct Client Technology</title>
		<link></link>
	</image>
	<description>
The one thing architects don’t have a shortage of these days are options, especially when it comes down to choosing the client technology that best suits their current project. Is it a web applications, or would be better to have it run natively on the desktop?
 Or perhaps a hybrid approach? In this episode of ARCast.tv, 
Denny Boynton talks with 
Brian Noyes, Chief Architect at 
iDesign, about what architects should consider when making decisions about which client technology to use. 
</description>
	<link></link>
	<language>en</language>
	<pubDate>Sun, 26 May 2013 09:44:14 GMT</pubDate>
	<lastBuildDate>Sun, 26 May 2013 09:44:14 GMT</lastBuildDate>
	<generator>Rev9</generator>
</channel>
</rss>