I have a .Net application running on a web farm that allows users to upload files and download them later via link to that file. Currently, I use Windows DFS to replicate the local IIS directory where the files are stored across the web farm servers
(/data). However, as this solution does not scale out, I want to implement a more scalable solution by partitioning the documents. Specifically, say I set up multiple file storage servers (Fs1, Fs2, Fs3, etc.) on the network. Further, let's
say I change my upload page to save the uploaded file to one of the file storage servers on the local LAN (based on some logic). I assume so far I am safe with ASP.NET doing this much assuming I have the correct permission for the ASP.NET process
ID. The question I have is with regards to download links. When a user gets served a download link to their document (e.g. http://www.testco.com/data/doc1.txt
) is there a way for me to "intercept"
that HTTP request and underneath the covers serve the doc1.txt from the file storage server (e.g. Fs2) it resides on? Any sample code would be appreciated. Thanks.
View Complete Post