<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://geeks.netindonesia.net/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>Eko Santoso - All Comments</title><link>http://geeks.netindonesia.net/blogs/santos2000id/default.aspx</link><description /><dc:language>en</dc:language><generator>CommunityServer 2007.1 (Build: 20917.1142)</generator><item><title>re: Microsoft Edan</title><link>http://geeks.netindonesia.net/blogs/santos2000id/archive/2007/11/21/microsoft-edan.aspx#24419</link><pubDate>Thu, 22 Nov 2007 11:44:13 GMT</pubDate><guid isPermaLink="false">5cc3a90d-ac9a-472a-8983-30514957434c:24419</guid><dc:creator>ES</dc:creator><description>&lt;p&gt;Ya, mungkin Pak Risman benar, ayo semangat belajar lagi.&lt;/p&gt;
&lt;img src="http://geeks.netindonesia.net/aggbug.aspx?PostID=24419" width="1" height="1"&gt;</description></item><item><title>re: Microsoft Edan</title><link>http://geeks.netindonesia.net/blogs/santos2000id/archive/2007/11/21/microsoft-edan.aspx#24417</link><pubDate>Thu, 22 Nov 2007 10:56:11 GMT</pubDate><guid isPermaLink="false">5cc3a90d-ac9a-472a-8983-30514957434c:24417</guid><dc:creator>Risman Adnan Mattotorang</dc:creator><description>&lt;p&gt;Ada dua kemungkinan, Microsoft terlalu cepat berinovasi atau developer adoption yang lambat. Tanpa inovasi di IT industri, akan terlibas sama inovasi lain. Natural kok. Biasanya tiap 18 bulan, pasti ada yang baru. &lt;/p&gt;
&lt;img src="http://geeks.netindonesia.net/aggbug.aspx?PostID=24417" width="1" height="1"&gt;</description></item><item><title>re: Domain Model VS Data Mapper</title><link>http://geeks.netindonesia.net/blogs/santos2000id/archive/2007/11/21/domain-model-vs-data-mapper.aspx#24409</link><pubDate>Thu, 22 Nov 2007 09:48:29 GMT</pubDate><guid isPermaLink="false">5cc3a90d-ac9a-472a-8983-30514957434c:24409</guid><dc:creator>ES</dc:creator><description>&lt;p&gt;My suggest is to combine between Data Manager and Domain model, so We don't have to break the principle of OOP, object have state and behaviour. &lt;/p&gt;
&lt;img src="http://geeks.netindonesia.net/aggbug.aspx?PostID=24409" width="1" height="1"&gt;</description></item><item><title>re: Microsoft Edan</title><link>http://geeks.netindonesia.net/blogs/santos2000id/archive/2007/11/21/microsoft-edan.aspx#24388</link><pubDate>Thu, 22 Nov 2007 01:58:56 GMT</pubDate><guid isPermaLink="false">5cc3a90d-ac9a-472a-8983-30514957434c:24388</guid><dc:creator>Agus Kurniawan</dc:creator><description>&lt;p&gt;jadinya nulisnya bukan Microsoft Edan tetapi &amp;quot;Keedanan Microsoft&amp;quot;&lt;/p&gt;
&lt;img src="http://geeks.netindonesia.net/aggbug.aspx?PostID=24388" width="1" height="1"&gt;</description></item><item><title>re: Domain Model VS Data Mapper</title><link>http://geeks.netindonesia.net/blogs/santos2000id/archive/2007/11/21/domain-model-vs-data-mapper.aspx#24311</link><pubDate>Wed, 21 Nov 2007 07:14:41 GMT</pubDate><guid isPermaLink="false">5cc3a90d-ac9a-472a-8983-30514957434c:24311</guid><dc:creator>Jimmy Chandra</dc:creator><description>&lt;p&gt;Frankly, I don't quite see the benefit of what is being suggested here. &amp;nbsp;Especially when your main argument is to just make the domain object look a little less &amp;quot;anemic&amp;quot;. &amp;nbsp;What is the real benefit?&lt;/p&gt;
&lt;p&gt;However, it's different if your CustomerManager is talking to a base / interface. That will certainly satisfy the need of doing something like this. since the actual implementation of an abstract Customer base class / interface will change between call. &amp;nbsp;This will allow flexibility in your design. &amp;nbsp;Just in case you have domains such as InternationalCustomer, DomesticCustomer, etc. which might be saved to a different table, or different validation rules, etc.&lt;/p&gt;
&lt;p&gt;Or if your CustomerManager is really a facade class that is doing more than just passing a single method call to the Domain object method. In this case, it is really a facade that will shield your API users from the inner working complexity of your Domain classes. ie. CustomerManager.DeleteCustomerOlderThan(DateTime date) which will might call Customer.Find method and iterate through it and do some checking and finally call Customer.Delete on each matching Customer object.&lt;/p&gt;
&lt;p&gt;Don't hate the skinny object just because it's skinny, hehehe. &amp;nbsp;Skinny object has its purpose too. Hehehe.&lt;/p&gt;
&lt;img src="http://geeks.netindonesia.net/aggbug.aspx?PostID=24311" width="1" height="1"&gt;</description></item><item><title>re: Microsoft Edan</title><link>http://geeks.netindonesia.net/blogs/santos2000id/archive/2007/11/21/microsoft-edan.aspx#24299</link><pubDate>Wed, 21 Nov 2007 05:30:42 GMT</pubDate><guid isPermaLink="false">5cc3a90d-ac9a-472a-8983-30514957434c:24299</guid><dc:creator>agusto xaverius</dc:creator><description>&lt;p&gt;Same with java khan banyak update an dari SDK pertama ampe akhir, cuman gw sich pikir kemajuan dan kemudahan development project makin hari makin bagus dengan .net ini.&lt;/p&gt;
&lt;p&gt;Pokoke bikin motto aja : Belajar tiada matinye&lt;/p&gt;
&lt;img src="http://geeks.netindonesia.net/aggbug.aspx?PostID=24299" width="1" height="1"&gt;</description></item></channel></rss>