http://www.microsoft.com/china/msdn/archives/Library/dnService/html/service07222003.asp
Matt PowellMicrosoft Corporation
July 22, 2003
Summary: Matt Powell describes how to eliminate performance issues that use Microsoft ASP.NET's Web Services Call with asynchronous methods and consumption issues of thread pool resources. (This article contains some links to English sites.)
Download the related sample code for this column.
In Microsoft, there is some interesting changes in the creation of Web content. As you may think, a lot of technical information you see on Microsoft.com requires participation from many people from Microsoft's different departments. Recently, those responsible for creating these contents, such as from product document groups, Microsoft Product Support Services (Most KnowledgeBases are generated by this), MSDN, and other groups, are reconsidering their content range. PSS first proposes this common problem, that is, the performance problem when the web service call is called from the ASP.NET web page. We feel that the problem beyond the range of KnowledgeBase articles, but it is not enough to form a product document. However, it is a good topic for the "At Your Service" column. Situation: Performance when calling Web services from ASP.NET Pages We expect Web services when discussing Web services in this column. A main situation is to access Web services from an intermediate layer environment (such as ASP.NET Web Pages). Users who provide support for Mappoint .NET Web services often receive such problems, that is, when the user uses its web service, the call to Mappoint .NET may require a considerable time. This is not a problem, but some other factors can make it a big problem than the surface.
