P
Paul
What is the best way to return to the calling code when calling a
asynchronous i/o call in C#. I have in other situations written
systems that were totally event driven so the callback fires an event.
My initial C# attempt has involved the callback re-calling the
origination function with a parameter object representing the modified
state i.e. call success and the next operation to perform. However I
am not sure what this is doing to the call-stack.
Is the method I am using correct?
Should I fire an event in the callback, delegated to calling function.
Should I block the calling function using a synchronising mechanism?
(How?)
asynchronous i/o call in C#. I have in other situations written
systems that were totally event driven so the callback fires an event.
My initial C# attempt has involved the callback re-calling the
origination function with a parameter object representing the modified
state i.e. call success and the next operation to perform. However I
am not sure what this is doing to the call-stack.
Is the method I am using correct?
Should I fire an event in the callback, delegated to calling function.
Should I block the calling function using a synchronising mechanism?
(How?)