c# - Open multiple text files from multiple servers ASP.NET -

First of all we have intranet to apologize for my bad English

work, we in Spnet Developed an application that has been duplicated on 4 servers, we have a computer that acts as a balancer that redirects the client to a specific server.

Permissions allow me to use only the Balancer and not the server where the page has been published.

The application contains automated processes that create a text file on each server in the path C:. \ Inetpub \ wwwroot \ ExportaPDF

If I enter the following path of a browser 10.48.203.1/ExportaPDF/Consulta_06102014.txt (to consider that relate to IP balancer Is) I see the content of the text file, but I can not control the server that I am using.

I need to create a page in ASP.NET which is repeated on every server that shows the contents of 4 servers. I mean you see the contents of text files:

  10.48.203.2/ExportaPDF/Consulta_06102014.txt 10.48.203.3/ExportaPDF/Consulta_06102014.txt 10.48.203.4/ExportaPDF/Consulta_06102014.txt 10.48.203.5 /ExportaPDF/Consulta_06102014.txt  

he had already said the problem is only accessible to balance (L0k48k203kl) and I wonder if there is any way to do it That is.

Thanks

I have to create a page in ASP. Repeats on each server on the Net which shows the content of 4 servers.

Option 1: You can add functionality to the server to get the files to the server can be loaded behind the balancer and direct access to all other servers You can add a button to the admin page to zip all the files and put it in a shared space. In this scenario, no matter what server your call is.

Option 2: Having all the servers using the same file can get you some concurrency problems Using a flat file to collect the data Best for production There is no option.

Option 4:

Option 3: You can automate this process by sending periodic emails to the server with files

Option 5: Add a new project to your solution with a simple HTTP endpoint For example, you can use the WebApi endpoint to fetch the data. The end point will be bound to a specific URL so that the balancer will not be a problem.

With so many options, we need more information to narrow it down ... you might want to check those and other options: to apply time, robustness, security (even if it's Intranet But, it may be a security concern that everyone on LAN can use those files), future compatibility etc.