Good question. I was under the impression he wants the processing to take place on a server and not to tie up the client machine. -----Original Message----- From: Steve Johnson [mailto:[EMAIL PROTECTED]] Sent: Friday, May 24, 2002 3:36 PM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] delegate\event\thread ?
> One last thing. What will make this fail is if the server goes down. PMFJI Why is a server required? The poster simply wants to know how to do asynchronous local processing on some data. I think what you want to do is: Client calls BO.Process BO.Process spawns a thread BO.Process returns to client BO thread performs processing BO raises done event back to client Just make sure that GUI developers realize that they are receiving the BO events on a different thread and need to use the InvokeRequired/Invoke methods in order to update GUI controls. You may want to define a RowProcess event and a Done event. You'll raise the RowProcess event for each row and then a done event at the end. This will allow the client developers to update for each row, if they desire to do so or ignore the RowProcess event and only listen to the Done event. You can consult the docs for how to implement events. -- Steve Johnson 3t Systems 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.
