M
Matthew Brown
Hi,
I am working with a COM library in which modifying almost every object
is done asynchronously (because the object represent physical devices
across a network somewhere on a telephone switch). Code to modify an
object, such as someObject.AddProperty("blah"); will execute
immediately but fire off an event when the change has actually been
completed.
I am developing an ASP.NET interface to this library. There will be
ways on some of our pages to modify objects on this device, using the
COM library. I would like to have the execution of the page actually
wait for the async "completed" event to fire before returning anything
to the user.
I'm having a hard time coming up with a way to do this - I feel like
I'm overlooking something simple. Any help?
I'm stuck on ASP.NET 1.1, btw.
I am working with a COM library in which modifying almost every object
is done asynchronously (because the object represent physical devices
across a network somewhere on a telephone switch). Code to modify an
object, such as someObject.AddProperty("blah"); will execute
immediately but fire off an event when the change has actually been
completed.
I am developing an ASP.NET interface to this library. There will be
ways on some of our pages to modify objects on this device, using the
COM library. I would like to have the execution of the page actually
wait for the async "completed" event to fire before returning anything
to the user.
I'm having a hard time coming up with a way to do this - I feel like
I'm overlooking something simple. Any help?
I'm stuck on ASP.NET 1.1, btw.