<?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>Hashtable.Clear thread-safety?</title><link>http://blogs.msdn.com/brada/archive/2003/04/13/49969.aspx</link><description>Q: Is it safe for a single writer to call Hashtable.Clear() with multiple concurrent readers? A: (from the developer that owns Hashtable) It depends on what you want. Clear() will not cause a hashtable to be inconsistent state, so hashtable will be not</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Synchronized .NET Collection Classes are NOT Thread Safe.</title><link>http://blogs.msdn.com/brada/archive/2003/04/13/49969.aspx#233360</link><pubDate>Thu, 23 Sep 2004 16:06:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:233360</guid><dc:creator>Marcus Mac Innes' Blog</dc:creator><description /></item></channel></rss>