<?xml version="1.0" encoding="UTF-8" ?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>PowerThreading at Yahoo! Groups</title>
    <link>http://tech.groups.yahoo.com/group/PowerThreading/</link>
    <description>Richter/Wintellect Power Threading</description>

    <item>
      <title>Re: AsyncEnumerator.BeginExecute</title>
      <pubDate>Sun, 08 Nov 2009 21:44:14 GMT</pubDate>
      <dc:creator>sgcvision</dc:creator>
      <link>http://tech.groups.yahoo.com/group/PowerThreading/message/614</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/PowerThreading/message/614</guid>
      <description>I have designed a class that acts like Figure 2 in your article http://msdn.microsoft.com/en-us/magazine/cc721613.aspx (except I&#39;m working with a Windows Form</description>
    </item>
    <item>
      <title>Re: AsyncEnumerator.BeginExecute</title>
      <pubDate>Sun, 08 Nov 2009 18:46:52 GMT</pubDate>
      <dc:creator>Jeffrey Richter (Wintellect LLC)</dc:creator>
      <link>http://tech.groups.yahoo.com/group/PowerThreading/message/613</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/PowerThreading/message/613</guid>
      <description>You are right about everything. If you care about catching an unhandled exception thrown from within the iterator, you need a try around the EndExecute method</description>
    </item>
    <item>
      <title>AsyncEnumerator.BeginExecute</title>
      <pubDate>Sun, 08 Nov 2009 18:43:55 GMT</pubDate>
      <dc:creator>sgcvision</dc:creator>
      <link>http://tech.groups.yahoo.com/group/PowerThreading/message/612</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/PowerThreading/message/612</guid>
      <description>I think I need a better understanding the AsyncCallback parameter of AsyncEnumerator.BeginExecute(). I understand that to be a callback method that the ae will</description>
    </item>
    <item>
      <title>Re: Unable to catch System.Net.Sockets.SocketException</title>
      <pubDate>Thu, 29 Oct 2009 02:28:06 GMT</pubDate>
      <dc:creator>Jeffrey Richter (Wintellect LLC)</dc:creator>
      <link>http://tech.groups.yahoo.com/group/PowerThreading/message/611</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/PowerThreading/message/611</guid>
      <description>The exception is being thrown from with9in an EndXxx method. You just have to put the EndXxx method in a try block and then you can catch the SocketException. </description>
    </item>
    <item>
      <title>Unable to catch System.Net.Sockets.SocketException</title>
      <pubDate>Thu, 29 Oct 2009 02:07:45 GMT</pubDate>
      <dc:creator>tmather99</dc:creator>
      <link>http://tech.groups.yahoo.com/group/PowerThreading/message/610</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/PowerThreading/message/610</guid>
      <description>I&#39;m playing around with the TcpServer example, and discovered that if the client terminated unexpectedly, TcpServer throw an exception inside Process() method</description>
    </item>
    <item>
      <title>Re: STA threads within AsyncEnumerator</title>
      <pubDate>Wed, 28 Oct 2009 19:38:21 GMT</pubDate>
      <dc:creator>Jeffrey Richter (Wintellect LLC)</dc:creator>
      <link>http://tech.groups.yahoo.com/group/PowerThreading/message/609</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/PowerThreading/message/609</guid>
      <description>The AsyncEnumerator never creates or spawns any thread on its own. I have not had to do what you are trying to do but what ever you would normally do should</description>
    </item>
    <item>
      <title>STA threads within AsyncEnumerator</title>
      <pubDate>Wed, 28 Oct 2009 19:35:45 GMT</pubDate>
      <dc:creator>king_perseus</dc:creator>
      <link>http://tech.groups.yahoo.com/group/PowerThreading/message/608</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/PowerThreading/message/608</guid>
      <description>I&#39;am using AsyncEnumerator to marshall calls into code paths that ultimately touch COM components, Wndows Imaging Components (WIC) to be exact. Calls to COM</description>
    </item>
    <item>
      <title>Re: New AsyncEnumerator feature I&#39;d like some feedback on</title>
      <pubDate>Wed, 21 Oct 2009 16:53:04 GMT</pubDate>
      <dc:creator>Jiri Cincura</dc:creator>
      <link>http://tech.groups.yahoo.com/group/PowerThreading/message/607</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/PowerThreading/message/607</guid>
      <description>Hi Jeffrey, your proposal looks interesting. On Wed, Oct 21, 2009 at 17:48, Jeffrey Richter (Wintellect LLC) ... From top of my head, what about some time</description>
    </item>
    <item>
      <title>New AsyncEnumerator feature I&#39;d like some feedback on</title>
      <pubDate>Wed, 21 Oct 2009 15:48:26 GMT</pubDate>
      <dc:creator>Jeffrey Richter (Wintellect LLC)</dc:creator>
      <link>http://tech.groups.yahoo.com/group/PowerThreading/message/606</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/PowerThreading/message/606</guid>
      <description>I&#39;m thinking of adding a feature to my AsyncEnumerator that would allow you to register two delegates with each AE object. The first &quot;SuspendCallback delegate&quot;</description>
    </item>
    <item>
      <title>Re: Named MutexResourceLocks</title>
      <pubDate>Tue, 13 Oct 2009 21:18:32 GMT</pubDate>
      <dc:creator>Paul Cross</dc:creator>
      <link>http://tech.groups.yahoo.com/group/PowerThreading/message/605</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/PowerThreading/message/605</guid>
      <description>Thanks Jeffrey.  I&#39;m managing concurrent access to an old-school  out-of-proc COM server so the standard .NET Mutex was the route I followed. All working fine</description>
    </item>
    <item>
      <title>Re: Named MutexResourceLocks</title>
      <pubDate>Tue, 13 Oct 2009 14:55:55 GMT</pubDate>
      <dc:creator>Jeffrey Richter (Wintellect LLC)</dc:creator>
      <link>http://tech.groups.yahoo.com/group/PowerThreading/message/604</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/PowerThreading/message/604</guid>
      <description>Usually, developers name a mutex so that it can be shared across process or AppDomain boundaries. However, my ResourceLock base class contains state that is</description>
    </item>
    <item>
      <title>Named MutexResourceLocks</title>
      <pubDate>Tue, 13 Oct 2009 12:56:28 GMT</pubDate>
      <dc:creator>Paul Cross</dc:creator>
      <link>http://tech.groups.yahoo.com/group/PowerThreading/message/603</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/PowerThreading/message/603</guid>
      <description>Hi, I&#39;m struggling with using the library.  Is there any way of creating a named mutex? Thanks, Paul</description>
    </item>
    <item>
      <title>Using .NET 4.0 Tasks with the AsyncEnumerator</title>
      <pubDate>Mon, 12 Oct 2009 13:17:37 GMT</pubDate>
      <dc:creator>Jeffrey Richter (Wintellect LLC)</dc:creator>
      <link>http://tech.groups.yahoo.com/group/PowerThreading/message/602</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/PowerThreading/message/602</guid>
      <description>I&#39;ve been doing a lot of work with the new Task class that ships with .NET 4.0 as I&#39;ve been revising my CLR via C# book (due out in early 2010). Task are</description>
    </item>
    <item>
      <title>The given assembly name or codebase was invalid (Exception from HRES</title>
      <pubDate>Mon, 12 Oct 2009 02:45:30 GMT</pubDate>
      <dc:creator>tmather99</dc:creator>
      <link>http://tech.groups.yahoo.com/group/PowerThreading/message/601</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/PowerThreading/message/601</guid>
      <description>I&#39;m keep getting the same error dialog whenever I tried to change the Wintellect.Threading.Silverlight.dll reference inside VS2008 SP1 for the</description>
    </item>
    <item>
      <title>Re: Will yield return 0 behave same with sync context?</title>
      <pubDate>Fri, 09 Oct 2009 03:13:08 GMT</pubDate>
      <dc:creator>Charles Prakash Dasari</dc:creator>
      <link>http://tech.groups.yahoo.com/group/PowerThreading/message/600</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/PowerThreading/message/600</guid>
      <description>Great, that answers my questions. Thank you Jeff! From: PowerThreading@yahoogroups.com [mailto:PowerThreading@yahoogroups.com] On Behalf Of Jeffrey Richter</description>
    </item>

  </channel>
</rss>
<!-- wr1.grp.sp2.yahoo.com uncompressed/chunked Mon Nov  9 13:19:02 PST 2009 -->
