About ThreadPool.Queu eUserWorkItem and ThreadPool.Regi sterWaitForSing leObject

[Henri]

Might sound a stupid question but need to be sure:

When you call ThreadPool.Queu eUserWorkItem and
ThreadPool.Regi sterWaitForSing leObject passing a New object as state

e.g.: ThreadPool.Queu eUserWorkItem(A ddressOf MyCallBack, New
MyObject(myArg1 , myArg2))

the new object MyObject is instantiated just before QueueUserWorkIt em is
called, and not just before MyCallBack is called, isn't it?
It's the same for RegisterWaitFor SingleObject, isn't it?

Thanks

Henri

[Scott Allen]

Yes, a reference to a brand new MyObject object will be passed into
the method. You also have to create the object before
RegisterWaitFor SingleObject.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Mon, 13 Dec 2004 14:34:16 +0100, "Henri" <hm********@hot mail.com>
wrote:

Might sound a stupid question but need to be sure:

When you call ThreadPool.Queu eUserWorkItem and
ThreadPool.Reg isterWaitForSin gleObject passing a New object as state

e.g.: ThreadPool.Queu eUserWorkItem(A ddressOf MyCallBack, New
MyObject(myArg 1, myArg2))

the new object MyObject is instantiated just before QueueUserWorkIt em is
called, and not just before MyCallBack is called, isn't it?
It's the same for RegisterWaitFor SingleObject, isn't it?

Thanks

Henri

[Henri]

Thanks,
So the new object will be instantied by the main thread, and MyCallBack will
then be processed by another thread from the threadPool, right?

Henri

"Henri" <hm********@hot mail.com> a écrit dans le message de
news:%2******** ********@TK2MSF TNGP14.phx.gbl. ..

Might sound a stupid question but need to be sure:

When you call ThreadPool.Queu eUserWorkItem and
ThreadPool.Regi sterWaitForSing leObject passing a New object as state

e.g.: ThreadPool.Queu eUserWorkItem(A ddressOf MyCallBack, New
MyObject(myArg1 , myArg2))

the new object MyObject is instantiated just before QueueUserWorkIt em is
called, and not just before MyCallBack is called, isn't it?
It's the same for RegisterWaitFor SingleObject, isn't it?

Thanks

Henri

[Scott Allen]

That's correct, Henri.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Mon, 13 Dec 2004 16:41:28 +0100, "Henri" <hm********@hot mail.com>
wrote:

Thanks,
So the new object will be instantied by the main thread, and MyCallBack will
then be processed by another thread from the threadPool, right?

Henri

"Henri" <hm********@hot mail.com> a écrit dans le message de
news:%2******* *********@TK2MS FTNGP14.phx.gbl ...

Might sound a stupid question but need to be sure:

When you call ThreadPool.Queu eUserWorkItem and
ThreadPool.Regi sterWaitForSing leObject passing a New object as state

e.g.: ThreadPool.Queu eUserWorkItem(A ddressOf MyCallBack, New
MyObject(myArg1 , myArg2))

the new object MyObject is instantiated just before QueueUserWorkIt em is
called, and not just before MyCallBack is called, isn't it?
It's the same for RegisterWaitFor SingleObject, isn't it?

Thanks

Henri

[Henri]

Thanks for your answers Scott :-) !

"Scott Allen" <bitmask@[nospam].fred.net> a écrit dans le message de
news:gs******** *************** *********@4ax.c om...

That's correct, Henri.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Mon, 13 Dec 2004 16:41:28 +0100, "Henri" <hm********@hot mail.com>
wrote:

Thanks,
So the new object will be instantied by the main thread, and MyCallBack willthen be processed by another thread from the threadPool, right?

Henri

"Henri" <hm********@hot mail.com> a écrit dans le message de
news:%2******* *********@TK2MS FTNGP14.phx.gbl ...

Might sound a stupid question but need to be sure:

When you call ThreadPool.Queu eUserWorkItem and
ThreadPool.Regi sterWaitForSing leObject passing a New object as state

e.g.: ThreadPool.Queu eUserWorkItem(A ddressOf MyCallBack, New
MyObject(myArg1 , myArg2))

the new object MyObject is instantiated just before QueueUserWorkIt em is called, and not just before MyCallBack is called, isn't it?
It's the same for RegisterWaitFor SingleObject, isn't it?

Thanks

Henri

[Douwe]

Henri wrote:

*Might sound a stupid question but need to be sure:

When you call ThreadPool.Queu eUserWorkItem and
ThreadPool.Regi sterWaitForSing leObject passing a New object as state

e.g.: ThreadPool.Queu eUserWorkItem(A ddressOf MyCallBack, New
MyObject(myArg1 , myArg2))

the new object MyObject is instantiated just before QueueUserWorkIt em
is
called, and not just before MyCallBack is called, isn't it?
It's the same for RegisterWaitFor SingleObject, isn't it?

Thanks

Henri *

-- I tried to use the RegisterWaitFor SingleObject function but delhpi
does not recognise the function variables... How did you solve this
problem.
( The WaitForSingleOb ject function is no problem)

thanks in advance

Douwe

--
Douwe
------------------------------------------------------------------------
Posted via http://www.codecomments.com
------------------------------------------------------------------------