Wilfried Mestdagh wrote:
> unit uJob
Thanks. Your piece of code will give me a good start off.
Lutz
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
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 = proc
--- Original Message -
From: "Lutz Schröer" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Thursday, November 03, 2005 3:26 AM
Subject: [twsocket] Design problem: function result and getAsync
> Hi,
>
> I've got a small design problem with the GetAs
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:
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:
unit1.pas:
--
functi
