Asynchronous operations, pinning

cbrumme s WebLog Asynchronous operations pinning | Insomnia Cure

cbrumme s WebLog Asynchronous operations pinning | Insomnia Cure — Wed, 10 Jun 2009 04:00:32 GMT

PingBack from http://insomniacuresite.info/story.php?id=3245

.NET Memory Management and GCHandle

From .NET Geek's Desk — Sun, 01 Mar 2009 10:59:25 GMT

GC Handle provides facilities to explicitly control and monitor the lifetime of an object in heap.Whenever

EndInvoke still required? | keyongtech

EndInvoke still required? | keyongtech — Thu, 22 Jan 2009 06:24:08 GMT

PingBack from http://www.keyongtech.com/433557-endinvoke-still-required

ASP.NET Tip: How to avoid creating a GC Hole

ASP.NET Debugging — Thu, 25 Sep 2008 15:52:03 GMT

There are only a few things that can make a .NET process crash.  The most common one is an Unhandled

blogging @ kafazov.net » Blog Archive » WinForms asyncronous programming model??????????????????? ????????????????????? ?? WinForms

Sun, 11 Mar 2007 16:05:57 GMT

PingBack from http://kafazov.net/blog/?p=116

Introducing ICommunicationObject

Nicholas Allen's Indigo Blog — Thu, 23 Feb 2006 22:02:24 GMT

In the Windows Communication Foundation, there are a few classes that are so fundamental that they are...

re: Concurrency, Part 13 - Concurrency and the CLR

Larry Osterman's WebLog — Fri, 25 Mar 2005 22:33:00 GMT

re: Asynchronous operations, pinning

Sharpie — Mon, 12 Jan 2004 19:39:00 GMT

Regarding the advice to call EndInvoke on all delegates or face potential resource leakage, I believe this was poorly conveyed in the docs until 1.1, and even then only barely mentioned.

Be that as it may, can you not get around this limitation for Fire and Forget by using the [OneWay] attribute on your delegate? I believe that attribute optimizes away the baggage of a fire and forget async delegate by preventing the runtime from having to carry around the IAsyncResult, the potential exception instance and the state object. So in short it kind of eliminates not only the concern of leakage but most of what it would leak anyway, and one would expect that if you had numerous such delegates, you'd be putting less strain on the resources. Presumably these are for operations for which don't throw exceptions or for which you don't care about their end result.

Incidentally, if that doesn't solve it and you still want to program with a fire and forget model, Mike Woodard of Developmentor implemented a smart class that takes care of calling EndInvoke for you. It is not the most performant thing but in small doses it could solve your fire and forget blues.

But something tells me that [OneWay] should take care of that for you, no?

RE: Asynchronous operations, pinning

Chris Brumme — Tue, 13 May 2003 00:30:00 GMT

I just got the official word from the WinForms team. It is not necessary to call Control.EndInvoke. You can call BeginInvoke in a "fire and forget" manner with impunity.

RE: Asynchronous operations, pinning

Dmitriy Zaslavskiy — Fri, 09 May 2003 16:42:00 GMT

Thanks Chris. I think I got it now.