Re: Asynchronous calls.

Could you set some global flag that each async. operation checks before
executing the real functionality?  Not as clean as removing the request, but
it would be a lot less work than doing your own removable thread queue.

Nick

----- Original Message -----
From: "Rolls, Robert" <[email protected]>
To: <[email protected]>
Sent: Friday, June 14, 2002 4:57 PM
Subject: Re: [DOTNET] Asynchronous calls.


> I need to stop outstanding request when my service is requested to stop.
>
> -----Original Message-----
> From: Nick Wienholt [mailto:[email protected]]
> Sent: Friday, 14 June 2002 16:45
> To: [email protected]
> Subject: Re: [DOTNET] Asynchronous calls.
>
>
> Asynchronous calls use the thread pool, which doesn't provide any methods
> for unqueueing pending work requests.  If you need to support cancellable
> asynchronous operations, the only option I can think of is running the
> method of a thread you create, and abort this thread if you no longer need
> the operation completed.  This technique may have more performance cost
than
> just letting the asynchronous method run through to completion, and
> disgrading the results - depends on the perf. cost of the asynchronous
> operation.
>
> Nick Wienholt
> Sydney Deep .NET User Group www.sdnug.org
>
>
> ----- Original Message -----
> From: "Rolls, Robert" <[email protected]>
> To: <[email protected]>
> Sent: Friday, June 14, 2002 1:56 PM
> Subject: [DOTNET] Asynchronous calls.
>
>
> > If I begin an asynchronous call the BeginXXX is it just a matter of
> calling
> > EndXXX if I want to cancel the outstanding call?
> >
> > Regards
> > Robert.
> >
> >
> >
> > **********************************************************************"
> > This correspondence is for the named person's use only. It may
> > contain confidential or legally privileged information or both. "
> > No confidentiality or privilege is waived or lost by any "
> > mistransmission.  If you receive this correspondence in error, please
> > immediately delete it from your system and notify the sender.  You
> > must not disclose, copy or rely on any part of this correspondence
> > if you are not the intended recipient.
> >
> > Any views expressed in this message are those of the individual sender,
> > except where the sender expressly, and with authority, states them to
> > be the views of Vodafone.
> >
> > This email has been checked for viruses.
> >
>
****************************************************************************
> ******************
> >
> > You can read messages from the DOTNET archive, unsubscribe from DOTNET,
or
> > subscribe to other DevelopMentor lists at http://discuss.develop.com.
>
> You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
> subscribe to other DevelopMentor lists at http://discuss.develop.com.
>
>
> **********************************************************************"
> This correspondence is for the named person's use only. It may
> contain confidential or legally privileged information or both. "
> No confidentiality or privilege is waived or lost by any "
> mistransmission.  If you receive this correspondence in error, please
> immediately delete it from your system and notify the sender.  You
> must not disclose, copy or rely on any part of this correspondence
> if you are not the intended recipient.
>
> Any views expressed in this message are those of the individual sender,
> except where the sender expressly, and with authority, states them to
> be the views of Vodafone.
>
> This email has been checked for viruses.
>
****************************************************************************
******************
>
> You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
> subscribe to other DevelopMentor lists at http://discuss.develop.com.
>

You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.