Printable View
Hi ,
The client code calls my dll and my dll writes into their o/p.
But the issue is , if there is long time, for my dll to do some processing, how to make sure the client looks into o/p after this processing is over. Because the o/p array might be half written
I was told that, the client waits for the function to end. But others arguing that, the array might be half baked !
thanks a lot for your inputs !
Pdk
The client code calls a function that is located within the .dll.
What is o/P?
output is pointer to memory location allocated by the client
Well if the called function writes to this memory, then presumably unless the function is threaded and returns whilst a background thread completes (asynchronous transfer), then when the function terminates and returns to the caller then all the writing required to the memory has been completed? Is the function single or multi-threaded? Is the transfer synchronous or asynchronous?
I think it is single threaded
It either is or is not. In programming you determine what is happening - you don't guess.Quote:
Originally Posted by pdk5
So why might the o/p be only half written when control is passed back to the caller?
because it is taking long to complete as it is just a function call and there is no way of knowing if o/p is written or not
It doesn't matter how long it takes to complete. Only the fact whether this "function" may or may not return before the writing has completed matters.Quote:
Originally Posted by pdk5
and whether it has completed successfully or not.
Agree! :thumb:Quote:
Originally Posted by 2kaud
Yes, my collegue came from multithreaded background and was confused about this.
Eventhough i havent worked on multithreading much, but i knew, in case of single thread this wont be issue. But couldnot argue further because of my limited computer programming knowledge.
But anyway thanks a lot kaud and victor. It is much appreciated.