Re: [twsocket] Design problem: function result and getAsync

2005-11-03 Thread Francois Piette
How do I have to design my unit so that I create a nice and simple function call in my main program but the actual code resides in a different unit? This is a perfect case where writing a component (or a class) is very helpful. In the component or class, you can encapsulate everything

Re: [twsocket] Design problem: function result and getAsync

2005-11-03 Thread Wilfried Mestdagh
Hello Lutz, Just write as always but you have a typical code that need to be executed in a separate object. So let the object behave as a normal ojbect. Later it is also very easy to use the thing in other applications. And you can use the normal async methods. unit uJob type TJobResult =

Re: [twsocket] Design problem: function result and getAsync

2005-11-02 Thread Arno Garrels
Lutz Schröer wrote: Hi, I've got a small design problem with the GetAsync method. My basic understanding is that after I called the getAsync method I have to do the further processing in httpRequestDone. This is no problem until I want to put the code in a different unit. For example: