<?xml version="1.0" encoding="utf-8" ?><rss version="2.0"><channel><title><![CDATA[Teddy's Knowledge Base]]></title><description><![CDATA[]]></description><link>https://blog.csdn.net/teddyma</link><language>zh-cn</language><generator>https://blog.csdn.net/</generator><copyright><![CDATA[Copyright &copy; teddyma]]></copyright><item><title><![CDATA[讨论：WCF可序列化的ActiveRecord实现有意义吗？]]></title><link>https://blog.csdn.net/teddyma/article/details/5797667</link><guid>https://blog.csdn.net/teddyma/article/details/5797667</guid><author>teddyma</author><pubDate>Sun, 08 Aug 2010 14:00:00 +0800</pubDate><description><![CDATA[<br />本文的目的，是探讨WCF可序列化的ActiveRecord实现是否有意义。ActiveRecord模式简介<br />ActiveRecord模式是Martin Fowler的企业应用架构模式中提到的一种数据访问模式，如下图：<br /><br />Person类包含lastName, firstName等这些属性，一个Person类的实例，对应数据库的一个Person表或视图的一条记录，每一个属性，对应数据库记录的一个字段；同时，Person类包含CRUD方法，封装了对数据库的操作；Perso]]></description><category></category></item><item><title><![CDATA[理解Design Pattern]]></title><link>https://blog.csdn.net/teddyma/article/details/5783950</link><guid>https://blog.csdn.net/teddyma/article/details/5783950</guid><author>teddyma</author><pubDate>Mon, 02 Aug 2010 20:00:00 +0800</pubDate><description><![CDATA[<br />本文的目的是以最精炼的语言，理解什么是Design Pattern，为什么需要Design Pattern，和关于Design Pattern的争论。什么是Design Pattern？<br />从字面上理解，Pattern，指的是解决常见问题的可重用的方案。Design，则限定了，这里的Pattern是为软件的设计服务的。因此，所谓Design Pattern，指的是解决常见的软件设计问题的可重用的方案，或者说解决方案的模板。<br /> <br />两点需要特别注意的是：算法不是Desig]]></description><category></category></item><item><title><![CDATA[理解O/R Mapping]]></title><link>https://blog.csdn.net/teddyma/article/details/5781691</link><guid>https://blog.csdn.net/teddyma/article/details/5781691</guid><author>teddyma</author><pubDate>Sun, 01 Aug 2010 00:00:00 +0800</pubDate><description><![CDATA[<br />本文的目的是以最精炼的语言，理解什么是O/R Mapping，为什么要O/R Mapping，和如何进行O/R Mapping。什么是O/R Mapping？<br />广义上，ORM指的是面向对象的对象模型和关系型数据库的数据结构之间的相互转换。<br />狭义上，ORM可以被认为是，基于关系型数据库的数据存储，实现一个虚拟的面向对象的数据访问接口。理想情况下，基于这样一个面向对象的接口，持久化一个OO对象应该不需要要了解任何关系型数据库存储数据的实现细节。为什么需要O/R Mapping？<]]></description><category></category></item><item><title><![CDATA[理解单元测试(Unit Testing)]]></title><link>https://blog.csdn.net/teddyma/article/details/5779682</link><guid>https://blog.csdn.net/teddyma/article/details/5779682</guid><author>teddyma</author><pubDate>Sat, 31 Jul 2010 15:01:00 +0800</pubDate><description><![CDATA[<br />本文的目的是以最精炼的语言，正解什么是单元测试，为什么要单元测试，和如何进行单元测试。 什么是单元测试(Unit Testing)？<br />测试(Testing)这个词很容易理解，那么什么是单元(Unit)呢？一个单元指的是应用程序中可测试的最小的一组源代码。一组源代码可测试，一般要求其有明确的输入和输出。因此，一般来讲，源代码中包含明确的输入和输出的每一个方法被认为是一个可测试的单元。注意，这里指的输出，并不局限于方法的返回值或对输入参数的改变，而包括了方法的执行过程中，改变的任何数据。为]]></description><category></category></item><item><title><![CDATA[正解TDD]]></title><link>https://blog.csdn.net/teddyma/article/details/5777786</link><guid>https://blog.csdn.net/teddyma/article/details/5777786</guid><author>teddyma</author><pubDate>Fri, 30 Jul 2010 01:01:00 +0800</pubDate><description><![CDATA[<br />本文的目的是以最精炼的语言，正解什么是TDD，为什么要TDD，和TDD的难点。 <br />什么是TDD？ 简单的说，TDD = 测试先行(TFD, Test First Development) + 重构(Refactoring) + 回归测试(Regression Test)。<br /><br /><br />如果要实现某个功能，TDD要求在初步定义完这个功能的外部接口之后，先根据这个功能的用例写测试代码(黑盒测试)，测试代码检验的是这个功能的外部接口的使用场景，而非具体的实现细节。然后，]]></description><category></category></item><item><title><![CDATA[讨论: TDD in HTML &amp; JavaScript 之可行性和最佳实践]]></title><link>https://blog.csdn.net/teddyma/article/details/5727736</link><guid>https://blog.csdn.net/teddyma/article/details/5727736</guid><author>teddyma</author><pubDate>Sun, 11 Jul 2010 22:00:00 +0800</pubDate><description><![CDATA[题外话<br />昨天就想发起这个话题的讨论，只是觉得对于讨论的支持，博客园现有的功能天然似乎还不能很好的支持。所以有了突然发现想在博客园发起一个有价值的讨论其实很难一文。亚历山大同志提到“博客园的讨论需要发起争议性话题，比如 .net sucks之类”。回顾如关于近期C#大论战的回应这样的近期引起讨论的焦点话题，貌似确实如此。深以为叹。近期的C#大论战是幸运的，尽管中间还是参杂了很多口水，李建忠老师的加入，一定程度上最终将话题引向了正确的方向。幸哉。我这个围观群众也从中获益良多。不仅仅是对于这个技术话题正]]></description><category></category></item><item><title><![CDATA[突然发现想在博客园发起一个有价值的讨论其实很难]]></title><link>https://blog.csdn.net/teddyma/article/details/5726288</link><guid>https://blog.csdn.net/teddyma/article/details/5726288</guid><author>teddyma</author><pubDate>Sat, 10 Jul 2010 20:01:00 +0800</pubDate><description><![CDATA[
			为什么会有如题的感叹呢?<br />其实,我们本来只是想和大家探讨一下TDD in HTML & JavaScript的可行性和最佳实践.<br /><br />首先想到用blog,可是,既然我只是想讨论,如果写一个blog一定很短,并且没有直接有价值的内容,所以,往首页放貌似是不合适的.但是不放首页其实没有几个人能看到的.就算我厚脸皮放到首页,也是很快就会被沉下去的.<br /><br />那么,别的呢?<br /><br />博问?看起来只是给新手问问题的?<br /><br />小组?我不得]]></description><category></category></item><item><title><![CDATA[This is jqMVC# – CNBLOGS Google Tracer Sample]]></title><link>https://blog.csdn.net/teddyma/article/details/5708122</link><guid>https://blog.csdn.net/teddyma/article/details/5708122</guid><author>teddyma</author><pubDate>Thu, 01 Jul 2010 23:00:00 +0800</pubDate><description><![CDATA[<br />In previous post - This is jqMVC# - Definition & Summary, I briefly introduced what is jqMVC#. In this post, I’ll show you a “CNBLOGS Google Tracer” sample application which is applying the jqMVC# architecture.Function<br /><br />“Google Tracer” is a]]></description><category></category></item><item><title><![CDATA[This is jqMVC# - Definition &amp; Summary]]></title><link>https://blog.csdn.net/teddyma/article/details/5682489</link><guid>https://blog.csdn.net/teddyma/article/details/5682489</guid><author>teddyma</author><pubDate>Sun, 20 Jun 2010 01:00:00 +0800</pubDate><description><![CDATA[<br />Before discussing more, please realize what I’m talking about is not “theoretical research”, but “real successful practice”.Definition<br />I created the word – “jqMVC#”, which means bunch of things:“j”  means it is about JavaScript;“q” means it is a]]></description><category></category></item><item><title><![CDATA[Discuss some new features in WCF 4.0]]></title><link>https://blog.csdn.net/teddyma/article/details/5528194</link><guid>https://blog.csdn.net/teddyma/article/details/5528194</guid><author>teddyma</author><pubDate>Sun, 25 Apr 2010 21:00:00 +0800</pubDate><description><![CDATA[			This article discusses my understanding of some new features in WCF 4.0 and how NIntegrate could work with WCF 4.0. 1. Configuration Based Activation “Configuration based activation” means, inste]]></description><category></category></item><item><title><![CDATA[Cross-Domain AJAX Enabled WCF Service]]></title><link>https://blog.csdn.net/teddyma/article/details/5353076</link><guid>https://blog.csdn.net/teddyma/article/details/5353076</guid><author>teddyma</author><pubDate>Sat, 06 Mar 2010 23:00:00 +0800</pubDate><description><![CDATA[			Background For the basic of how to create an AJAX enabled WCF service, please refer to MSDN: http://msdn.microsoft.com/en-us/library/bb924552.aspx. For the basic of JSONP, please refer to: http:/]]></description><category></category></item><item><title><![CDATA[LRU Caching Practice]]></title><link>https://blog.csdn.net/teddyma/article/details/5324174</link><guid>https://blog.csdn.net/teddyma/article/details/5324174</guid><author>teddyma</author><pubDate>Wed, 24 Feb 2010 22:00:00 +0800</pubDate><description><![CDATA[			In this article, let’s practice applying LRU caching in an enterprise application for different business cases. Background Firstly, let’s assume we have a User table in database and there may be ]]></description><category></category></item><item><title><![CDATA[Enterprise Caching Summary]]></title><link>https://blog.csdn.net/teddyma/article/details/5321056</link><guid>https://blog.csdn.net/teddyma/article/details/5321056</guid><author>teddyma</author><pubDate>Tue, 23 Feb 2010 23:00:00 +0800</pubDate><description><![CDATA[			Background Caching is an very important topic in enterprise-level multi-tier application, especially for web application. A general rule for applying caching is you should consider do necessary c]]></description><category></category></item><item><title><![CDATA[NIntegrate SOA Practice – E-Appointments Sample Application]]></title><link>https://blog.csdn.net/teddyma/article/details/5313639</link><guid>https://blog.csdn.net/teddyma/article/details/5313639</guid><author>teddyma</author><pubDate>Sat, 20 Feb 2010 22:00:00 +0800</pubDate><description><![CDATA[			E-Appointments  is a Microsoft ASAP (Aspiring Software Architects Program) Case Study  Implementation using the latest .NET 3.0 Technologies and proven  Microsoft patterns and practices like Soft]]></description><category></category></item><item><title><![CDATA[NIntegrate v0.9.0.1 released]]></title><link>https://blog.csdn.net/teddyma/article/details/5285808</link><guid>https://blog.csdn.net/teddyma/article/details/5285808</guid><author>teddyma</author><pubDate>Sat, 23 Jan 2010 01:32:00 +0800</pubDate><description><![CDATA[			Project Site:http://nintegrate.comDownload: Download from SVN 		Download from Google Code 		Download from CodePlex ]]></description><category></category></item><item><title><![CDATA[.NET Enterprise SOA – NIntegrate Practice]]></title><link>https://blog.csdn.net/teddyma/article/details/5285807</link><guid>https://blog.csdn.net/teddyma/article/details/5285807</guid><author>teddyma</author><pubDate>Wed, 20 Jan 2010 21:32:00 +0800</pubDate><description><![CDATA[			NIntegrate is open source .NET enterprise SOA framework. It provides several reusable SOA components to solve specific enterprise SOA problems. Different from some other one-in-one SOA solution, ]]></description><category></category></item><item><title><![CDATA[Enterprise WCF - Integrate WCF Configuration into Your Enterprise Framework]]></title><link>https://blog.csdn.net/teddyma/article/details/4605840</link><guid>https://blog.csdn.net/teddyma/article/details/4605840</guid><author>teddyma</author><pubDate>Fri, 28 Aug 2009 23:30:00 +0800</pubDate><description><![CDATA[			Background Lots of people declares they are using WCF in their “enterprise” distributed software development together with other SOA technologies, and even calls their software architecture WCF b]]></description><category></category></item><item><title><![CDATA[NIntegrate近期动态08/06]]></title><link>https://blog.csdn.net/teddyma/article/details/4605842</link><guid>https://blog.csdn.net/teddyma/article/details/4605842</guid><author>teddyma</author><pubDate>Thu, 06 Aug 2009 09:30:00 +0800</pubDate><description><![CDATA[			NIntegrate (http://nintegrate.com/) 是Teddy近期在维护的开源SOA开发框架。原本计划在近期能达到1.0版本，不过，在0.8之后，经过很多深入的思考和工作中的相关应用实践，决定进行较大的重构，或者说重新设计更合适。以下是在0.9中将包含的部分重大修改：    首先，新设计的核心模块不再依赖并默认提供基于SQL Server数据库的集中化配]]></description><category></category></item><item><title><![CDATA[AdoNet vs LinqToSql vs NIntegrateQuery查询性能测试]]></title><link>https://blog.csdn.net/teddyma/article/details/4605844</link><guid>https://blog.csdn.net/teddyma/article/details/4605844</guid><author>teddyma</author><pubDate>Sun, 07 Jun 2009 01:30:00 +0800</pubDate><description><![CDATA[			AdoNet vs LinqToSql vs NIntegrateQuery查询性能测试. 先上测试结果: AdoNetTest: 267msAdoNetCachedCommandTest: 182msLinqToSqlTest: 3191msLinqToSqlCompiledQueryTest: 386msNIntegrateQueryTest: 266ms 下载 下载测试数据库：Ad]]></description><category></category></item><item><title><![CDATA[提前发布4/25上海俱乐部活动演讲&ldquo;集中化WCF服务配置管理&rdquo;示例程序]]></title><link>https://blog.csdn.net/teddyma/article/details/4605847</link><guid>https://blog.csdn.net/teddyma/article/details/4605847</guid><author>teddyma</author><pubDate>Tue, 21 Apr 2009 00:30:00 +0800</pubDate><description><![CDATA[			承蒙4/25上海俱乐部活动组织团队邀请，本人有幸将在本次活动中和大家分享一下“集中化WCF服务配置管理”方面的一些探索。为了让大家对活动当天我讲的话题提前有一个更直观的了解，在这里提前介绍一下到时我会演示的示例程序。  本示例程序具体演示如下内容： 1) 基于SQL Server数据库的集中化WCF服务配置管理;  2) 集中化ConnectingString管理;  3) 集中化App]]></description><category></category></item></channel></rss>