IIS and DFS interactivity

dzim · 03-03-2008, 01:12 PM

Let us say we have a centrally located Database server, a file repository and a WebApp server running IIS 6.0 in location A. Let's then say there is a remote file repository and a remote user (of the web app) in location B far far away.

The file repositories in loc A and B are 'synced' using DFS and its namespace capability. Our webapp uses the AspUpload module for file access, upload, and deletion.

Now the question. If a user in location B tries to access or upload a file to the namespace (which will find the least expensive path and direct the user to the local file repository in loc B), will the data actually go 'through' the WebApp machine in loc A? Or will IIS actually 'hand off' the file transfer business to the user and the repository in loc B, therefore leaving itself out of the actual transfer?

If this is the case, the transfer for the user at loc B will be 'local' and therefore fast. If not, the data will literally have to go from file repository B, through WebApp A, and BACK to user B, and making it much slower.

Thanks to anybody who can help!

Derek Zimmermann M.S.C.S.
Application developer II
Epsilon Systems Solutions

03-03-2008, 01:12 PM	#1 (permalink)
dzim Registered User Join Date: Mar 2008 Posts: 1 OS: Windows Server 2003	IIS and DFS interactivity Let us say we have a centrally located Database server, a file repository and a WebApp server running IIS 6.0 in location A. Let's then say there is a remote file repository and a remote user (of the web app) in location B far far away. The file repositories in loc A and B are 'synced' using DFS and its namespace capability. Our webapp uses the AspUpload module for file access, upload, and deletion. Now the question. If a user in location B tries to access or upload a file to the namespace (which will find the least expensive path and direct the user to the local file repository in loc B), will the data actually go 'through' the WebApp machine in loc A? Or will IIS actually 'hand off' the file transfer business to the user and the repository in loc B, therefore leaving itself out of the actual transfer? If this is the case, the transfer for the user at loc B will be 'local' and therefore fast. If not, the data will literally have to go from file repository B, through WebApp A, and BACK to user B, and making it much slower. Thanks to anybody who can help! Derek Zimmermann M.S.C.S. Application developer II Epsilon Systems Solutions