[twsocket] Asychronous opperation of Over Byte components - Automated processes

2011-02-15 Thread Brennan, Stephen
How should one go about coding a user initiated automated/interactive processes which use TTnCnx and TTFtpClient? The user must be able to cancel the process and respond to prompts as required by the process. If one uses On... events to trigger the next step the code become part of the GUI

Re: [twsocket] Asychronous opperation of Over Byte components - Automated processes

2011-02-15 Thread Brennan, Stephen
I will add that the wait process could simply be a periodic check (e.g FtpClient.State=ftpReady) amongst other code in the thread. Regards Stephen From: Stephen Sent: Wednesday, 16 February 2011 8:46 AM To: 'twsocket@elists.org' Subject: Asychronous opperation of Over Byte components -

Re: [twsocket] Asychronous opperation of Over Byte components-Automated processes

2011-02-16 Thread Brennan, Stephen
Thank you for your advice. Am I right in saying that your asynchronous design pattern would treat each automated process as an object with inputs and outputs but this objects code should only be executed as part of the main thread? I.e. I think using a TDataModule in this manner is essential the