<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
  <channel>
    <title>DotNetKicks.com : Stories kicked by arnonrgo</title>
    <description>Stories kicked by arnonrgo</description>
    <link>http://www.dotnetkicks.com/</link>
    <language>en-us</language>
    <copyright>Atweb Publishing Ltd.</copyright>
    <docs>http://backend.userland.com/rss</docs>
    <generator>DotNetKicks.com - .NET links, community driven</generator>
    <ttl>30</ttl>
    <item>
      <title>Refactoring the GoF patterns</title>
      <description>In other words Concrete patterns* (like GoF's) are tied to implementation which means that the implementation language is  part of their &amp;quot;context&amp;quot;. Thus when you come to apply a pattern in a different language you need to consider the language in use and make sure that

   1. The pattern is needed
   2. The solution in the pattern is the best one for the language. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.rgoarchitects.com%2fnblog%2f2008%2f04%2f22%2fRefactoringTheGoFPatternsSingletonInNETContinued.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.rgoarchitects.com%2fnblog%2f2008%2f04%2f22%2fRefactoringTheGoFPatternsSingletonInNETContinued.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/patterns/Refactoring_the_GoF_patterns</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/patterns/Refactoring_the_GoF_patterns</guid>
      <pubDate>Wed, 23 Apr 2008 12:20:25 GMT</pubDate>
    </item>
    <item>
      <title>Singleton in .NET</title>
      <description>A proper way for implementing the singleton in .NET &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.rgoarchitects.com%2fnblog%2f2008%2f03%2f31%2fSingletonInNET.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.rgoarchitects.com%2fnblog%2f2008%2f03%2f31%2fSingletonInNET.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/csharp/Singleton_in_NET</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/csharp/Singleton_in_NET</guid>
      <pubDate>Thu, 03 Apr 2008 19:16:55 GMT</pubDate>
    </item>
    <item>
      <title>RESTful WCF</title>
      <description>If you are a .NET developer/architect and wanted you may know that to implement a RESTful application in Windows Communication Foundation (WCF) you really have to jump through hoops.For instance  you have to go back to basics and use the HttpRequest and HttpResponse, handle the breakdown and parsing of URI hierarchies yourself not to mention  fight  with the  bindings .

Fortunetly this all changed with WCF 3.5. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.rgoarchitects.com%2fnblog%2f2008%2f03%2f12%2fRESTfulWindowsCommunicationFoundationWCF.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.rgoarchitects.com%2fnblog%2f2008%2f03%2f12%2fRESTfulWindowsCommunicationFoundationWCF.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/webservices/RESTful_WCF</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/webservices/RESTful_WCF</guid>
      <pubDate>Thu, 13 Mar 2008 15:57:25 GMT</pubDate>
    </item>
  </channel>
</rss>