>Our channel of communications(network) collapses, due to the home page is very heavy; for the whole logic that manages. This has put under an obligation to change the philosophy of the application web and instead of making direct reference to the server of the type files JS and CSS; we had to place the files locally in the pc of the users that use the application.
>
>This action results us in:
>1.- If the user is new and he doesn't have the files in his machine the application it doesn't work correctly.
>2.- If we have updated the files, the users don't have the way of knowing that the files have changed.
>
>
>
>The objective is:
>1.- In case the directory and the files don't exist, the application should show the user a message and to inform them that they doesn't have installed the files and that it cannot continue.
>2.- In case the directory exists and the files are outdated, the application should discharge the new files and to overwrite the existent ones.
>
>Does anybody know any way to resolve the troblue?
>
>TIA

Beef up the server or get a bigger pipe. Moving source code to the client is a bad idea. The .js files are already cached on the user's PC. There is no dependable way to reference the files locally with an Include tag.

You might consider using a javascript stub in the home page that loads the content dynamically after the static portion of the page is returned to the browser. You can see this type of behavior on the msn.com home page. All of the static elements of the page are rendered by the browser. Then the javascript calls back to a web service and inserts the dynamic content into the DOM when it becomes available. It slows down the total time that it takes for the entire page to be displayed, but it feels like it is quicker because the static elements are rendered immediately.