![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
If I have a COM+ method that returns results from a long-running database query, is there a way to create a version of the method that uses one of the .NET asynchronous calling patterns? Assume that I can use any technology I like. My interest is in creating asynchronous web pages for use in a high-volume web application. It's a bad idea to block the ASP.NET worker threads by, for instance, blocking on a COM+ method call. |
#3
| |||
| |||
|
|
If I have a COM+ method that returns results from a long-running database query, is there a way to create a version of the method that uses one of the .NET asynchronous calling patterns? Assume that I can use any technology I like. My interest is in creating asynchronous web pages for use in a high-volume web application. It's a bad idea to block the ASP.NET worker threads by, for instance, blocking on a COM+ method call. Since Windows 2000, COM has supported asynchronous method calls. See http://msdn.microsoft.com/msdnmag/issues/0400/async/. Note that the implementation for the asynchronous architecture is confined to the proxy, so this should work just fine with COM+ objects. Personally, I have never used this support, preferring instead to launch a worker thread internal to the COM+ object to do my asynchronous work. Obviously you can do the same. |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |