RE: [cobalt-users] Trouble disabling ASP script caching (RAQ4) RESOLVED

["Landon Jenkins" <llj001@xxxxxxxxxxx>]

>> After further research, I have found Chilisoft documentation 
>> that explains the issue, although it has nothing to do with 
>> the script caching setting. Here's a snippet of the doc... 
>> 
>> <snip> 
>> 
>> Often after you edit an "included" file, the change does not 
>> show up in your ASP page. The ASP Server only picks up 
>> changes in an included file if it recompiles the page that 
>> contains the #include directive. You can force a recompile of 
>> this page by "touching" the file or by making a trivial 
>> change that updates the timestamp on the file. 
>> 
>> </snip> 
>> 
>> This is quite an inconvenience but apparently something we 
>> must live with. 
> 
>
>Would it make a difference if the included file was a .shtml file or 
>wouldn't that get processed as .shtml in the asp include? 

I'm no authority on the subject, but based on my observation, my best guess is that the first time an ASP page is called, the results (including the contents of the include file) are displayed to the user and also stored in memory on the ASP server itself. So long as the timestamp hasn't changed for the ASP page, each subsequent request for the page will be served from memory rather than actually going through the process of parsing the ASP page itself.

Really, this goes back to my original issue with trying to disable script caching. My guess is that if I were able to actually disable script caching, this "fix" wouldn't be necessary. 

Landon