]
Subject: Re: [ADVANCED-DOTNET] Async Data Commands with ADO.Net
But what's wrong with creating a thread? If you use the threadpool it's
almost a one-liner! (Aside from the stub you'll prob have to write..)
I guess it's personal preference whether you prefer to use special async
APIs or whether
snip
But what's wrong with creating a thread? If you use the
threadpool it's almost a one-liner!
Although if you use the threadpool you almost certainly won't be
creating a thread - you'll just be using a thread that was already in
the thread pool most of the time.
And that's typically a good
(result);
}
Hope that helps.
-Mensaje original-
De: Moderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] En nombre
de Brian Gaer
Enviado el: miércoles, 08 de octubre de 2003 1:09
Para: [EMAIL PROTECTED]
Asunto: [ADVANCED-DOTNET] Async Data Commands with ADO.Net
Is anyone
-
From: Moderated discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Gaer
Sent: Tuesday, October 07, 2003 7:09 PM
To: [EMAIL PROTECTED]
Subject: [ADVANCED-DOTNET] Async Data Commands with ADO.Net
Is anyone familiar with a method to have an ADO.Net command object
perform
- Original Message -
From: Brian Gaer [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, October 07, 2003 6:08 PM
Subject: [ADVANCED-DOTNET] Async Data Commands with ADO.Net
Is anyone familiar with a method to have an ADO.Net command object
perform a command.ExecuteNonQuery
Jade Burton wrote:
But what's wrong with creating a thread? If you use the
threadpool it's almost a one-liner!
Although if you use the threadpool you almost certainly won't be
creating a thread - you'll just be using a thread that was already in
the thread pool most of the time.
And that's
In keeping with Ian's comment, look at Bob Beauchemin's Essential ADO.NET,
Chapter 3. He has a section on cancellation where he says that *if* you do
wish the command to be cancelable, you need to both:
1. start the command on a separate thread, and
2. issue the cancel command on an additional
Is anyone familiar with a method to have an ADO.Net command object
perform a command.ExecuteNonQuery() asynchronously?
The Stored Proc I am calling takes from 2 to 10 minutes to return, and I
cannot wait for it and do not care what the results of the query are.
I searched all over and the only
of the threads in my app (or have that option in the future.)
Jade Burton
-Original Message-
From: Moderated discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] Behalf Of Brian Gaer
Sent: Wednesday, 8 October 2003 9:09 AM
To: [EMAIL PROTECTED]
Subject: [ADVANCED-DOTNET] Async Data Commands
