<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Logical splits across tiers</title><link>http://blogs.msdn.com/toddmck/archive/2004/02/20/77065.aspx</link><description>Sam Gentile posted an entry to his blog that really has me thinking. I understand his position to be that most of the books, blogs, docs, etc... on .NET have developers creating client/server applications, and that the Java community truly &amp;#8220;thinks</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Logical splits across tiers</title><link>http://blogs.msdn.com/toddmck/archive/2004/02/20/77065.aspx#77108</link><pubDate>Fri, 20 Feb 2004 18:04:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:77108</guid><dc:creator>DonXML Demsak</dc:creator><description>Keep up the discussions!  I agree with Sam, there are lots and lots of developers out there that don't care about architecture.  This impression comes from years of doing User Group work.  That's part of the reason why VB was so popular, anyone (well almost anyone) could code, and did.  Lots of those same folks are still coding, not looking to improve their knowledge base, and do .Net developement the same way they did VB development.  That is why it is so important to get application blocks out to the masses, so they don't have to think (much) about all the complexities of architecture, and just clone and go (well for the most part).&lt;br&gt;&lt;br&gt;Don</description></item><item><title>re: Logical splits across tiers</title><link>http://blogs.msdn.com/toddmck/archive/2004/02/20/77065.aspx#77116</link><pubDate>Fri, 20 Feb 2004 18:31:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:77116</guid><dc:creator>Sam Gentile</dc:creator><description>As my good friend DonXML says, my experience has been a great many .NET developers don't care or know about architecture. I do plan to revise my topic quite a bit though and clarify things I was trying to say. You may want to check out all the ES posts I and Robert Hurlbut are doing already as we live in this stuff every day.</description></item><item><title>re: Logical splits across tiers</title><link>http://blogs.msdn.com/toddmck/archive/2004/02/20/77065.aspx#77276</link><pubDate>Fri, 20 Feb 2004 22:23:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:77276</guid><dc:creator>Udi Dahan - The Software Simplist</dc:creator><description>I find the use of automatic transactions to be a very important plus for the use of ES. If you've ever had to do manual transaction management ( passing around transaction objects between BL objects ), you'll quickly see the benefit.&lt;br&gt;&lt;br&gt;When you tie automatic transactions together with SOA ( at least the &amp;quot;Ripping Sh!t Apart&amp;quot; aspect of SOA as stated on my blog ) it greatly simplifies the system. I've promised DevX to write an article on this, but haven't gotten around to it yet.&lt;br&gt;&lt;br&gt;IMHO, automatic transactions are enough of a reason to start using ES, even without understanding all of the more intricate details of it. Note that this is most pertinent for large-scale/enterprise development systems. &amp;quot;Drag and drop a table from the server explorer on a webform&amp;quot; type systems will probably benefit less.</description></item></channel></rss>