It's okay. The sample on my site he referred to is specifically a "safe" way to do fire-and-forget without leaking. I put that sample up in response to the discovery on 1.1 that just calling BeginInvoke was potentially dangerous.
-Mike http://www.bearcanyon.com > -----Original Message----- > From: Moderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of > John St. Clair > Sent: Friday, October 10, 2003 4:09 AM > To: [EMAIL PROTECTED] > Subject: Re: [ADVANCED-DOTNET] Async Data Commands with ADO.Net > > I think Mike (and Ian, and some others) have reconsidered > that pattern, > after some feedback from MS /changes in the documentation in > 1.1 on this. In > particular, IIRC, there was the possibility of leakage when > not calling > EndInvoke. Check the archives for more information... > > John > > -----Original Message----- > From: Moderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of > Erymuzuan Mustapa > Sent: 10. oktober 2003 04:54 > To: [EMAIL PROTECTED] > Subject: Re: Async Data Commands with ADO.Net > > Well, if you don't care about the result and want to take care of the > thread, take a look at Woodring's fire and forget > http://staff.develop.com/woodring/dotnet/#FireAndForget > > Regard > Erymuzuan Mustapa > =================================== This list is hosted by DevelopMentorŪ http://www.develop.com NEW! ASP.NET courses you may be interested in: 2 Days of ASP.NET, 29 Sept 2003, in Redmond http://www.develop.com/courses/2daspdotnet Guerrilla ASP.NET, 13 Oct 2003, in Boston http://www.develop.com/courses/gaspdotnet View archives and manage your subscription(s) at http://discuss.develop.com
