Geeks With Blogs
Khurram Aziz All In All Its Just Another Brick In The Wall!
| Home |

There is an old application hosted on the application server at my job. The core COM+ application was exposed over HTTP using ASP and XML. The custom ASP scripts are used parsing XML requests using MSXML. It was a long time ago when SOAP was not made available.

 

This web-service like approach was required as two other web application hosted on two physically different nodes need to communicate with it. One of these web applications is hosted in a shared hosting environment, and we did not wanted to involve in DLL-Hell syndrome. We opted MSXML SDK for the communication. We used the similar approach for the other web application to use the same code base.

 

The interesting thing that I want to point out here is, if you use MSXML SDK to communicate, it uses Internet Explorer web surfing engine in the back end. The Internet Explorer web surfing engine creates and maintains the temporary internet files, cookies and other such stuff. Generally, web applications run under IWAM user, and as IWAM user do not have the user profile, so there is no simple workout to set Internet Explorer settings (smaller temporary file cache etc).

 

For this reason, the IE files continue to be generated and at one stage web application starts getting slow. For instance, here at the server, these files are generated in the subfolders with names Cookies, History and Temporary Internet Files under %TEMP% (C:\WINNT\TEMP). To get the performance back, we need to shutdown the web application, delete these files and re-start the web application.

 

I am not sure which API do Web Services Proxies of Microsoft.NET use; if they are using MSXML then I guess this problem might occur in ASP.NET application.

Posted on Thursday, June 10, 2004 1:22 PM Windows DNA | Back to top


Comments on this post: MSXML and Temporary Internet FIles

No comments posted yet.
Your comment:
 (will show your gravatar)


Copyright © Khurram Aziz | Powered by: GeeksWithBlogs.net