About ThreadPool.QueueUserWorkItem and ThreadPool.RegisterWaitForSingleObject

[Henri]

Might sound a stupid question but need to be sure:

When you call ThreadPool.QueueUserWorkItem and
ThreadPool.RegisterWaitForSingleObject passing a New object as state

e.g.: ThreadPool.QueueUserWorkItem(AddressOf MyCallBack, New
MyObject(myArg1, myArg2))

the new object MyObject is instantiated just before QueueUserWorkItem is
called, and not just before MyCallBack is called, isn't it?
It's the same for RegisterWaitForSingleObject, 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
RegisterWaitForSingleObject.

 

[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

 

[Scott Allen]

That's correct, Henri.

 

[Henri]

Thanks for your answers Scott !

That's correct, Henri.

 

[Douwe]

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

When you call ThreadPool.QueueUserWorkItem and
ThreadPool.RegisterWaitForSingleObject passing a New object as state

e.g.: ThreadPool.QueueUserWorkItem(AddressOf MyCallBack, New
MyObject(myArg1, myArg2))

the new object MyObject is instantiated just before QueueUserWorkIte
is
called, and not just before MyCallBack is called, isn't it?
It's the same for RegisterWaitForSingleObject, isn't it?

Thanks

Henri *

-- I tried to use the RegisterWaitForSingleObject function but delhp
does not recognise the function variables... How did you solve thi
problem.
( The WaitForSingleObject function is no problem)

thanks in advance

Douw


-
Douw