Actually, I implemented an AsyncSqlAppender. On Thu, Jun 14, 2012 at 12:34 PM, George Chung <[email protected]> wrote:
> Yes, and when you submit async operations, those async requests are queued > by the runtime and the completion routines are executed by threads from > this thread pool. No need to manage threads at all. I did a pretty trivial > hack to the AdoNetAppender to perform Async Sql inserts and it's been > working flawlessly in our production environment. > > I'll attach the modified files shortly. > > > On Fri, Jun 8, 2012 at 4:32 AM, Stefan Bodewig <[email protected]> wrote: > >> On 2012-06-08, Christian Grobmeier wrote: >> >> > Hi, >> >> > On Fri, Jun 8, 2012 at 8:39 AM, Dominik Psenner <[email protected]> >> wrote: >> >> >> * the ThreadPool should be used in favour over a designated worker >> Thread >> >> > no idea becuase I have no clue on .NET, but it sounds like fun :-) >> >> .Net has a built-in thread pool it uses for all kinds of internal stuff, >> including async executions of user events or serving ASP.NET requests - >> and it provides access to it for user code. Rather than creating new >> ad-hoc Threads you re-use one of the pool. >> >> Stefan >> > >
