<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>AnalyticGal - Code Blog comments</title>
    <link>http://code.analyticgal.com/</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>AnalyticGal - Code Blog comments</description>
    <item>
      <title>"RC2 Performance Enhancements" by Scott Hughes</title>
      <description>In general, I'd recommend against synchronizing with "lock(this)".  The reason is that the object this method is encapsulated by could be used by external methods for locking, thus starving your encryption method.  It's good form to create a private internal object (I usually call mine lockObject, with something more descriptive used only if I need more than one) and synchronize only on this internal object.  That way, your object itself will have total control over it's lock.  It would be a nasty unintended side-effect if a consumer of an object discovered by chance that his call to your encryption method was blocking forever...</description>
      <pubDate>Wed, 24 Aug 2005 21:12:41 PDT</pubDate>
      <guid>http://code.analyticgal.com/articles/2005/06/13/rc2-performance-enhancements#comment-1</guid>
      <link>http://code.analyticgal.com/articles/2005/06/13/rc2-performance-enhancements#comment-1</link>
    </item>
  </channel>
</rss>
