NT 8 Conversion

[Gordon Holfelder]

Hi All-

Been a while since I've posted here, but here goes.

Finally moved from NT5 all the way to 8. Broke a few things along the way, but all seems to be working fine now. The only exception is something that is mostly annoying;

We use a lot of custom javascript files in the development process. After I've made a change to any of these files, I usually press CTRL-F5 to force a refresh in the browser to continue testing and/or debugging of the javascript. Instead of the changed js file being loaded, the original is loaded again.

This was not happening with NT5. In addition, the framework we're using dynamically loads the js files and provides a cache-busting argument on the url as in: http://localhost:88/ep/lib/ux/UpdateButtons.js?_dc=1399325165969 that doesn't seem to have any effect.

The only way I can get the new js file to load is to restart the web server.

Is there some caching going on in the nt server? Is there a setting that would fix this?

Thanks,
Gordon

[Bruce]

Hi Gordon,

>> Is there some caching going on in the nt server?

yes.

>> Is there a setting that would fix this?

Yes. WebServer Procedure, Performance Tab. "Enable Cache".

Cheers
Bruce

[Gordon Holfelder]

Hello Bruce-

Thanks!

BTW, wouldn't it make sense to cache on the url including arguments instead of just the file name? For me this means I wouldn't have to change between production and test modes. In production mode the cache busting doesn't happen from the client side.

Or perhaps look to see if the date of the file has changed.

Regards,
Gordon

[Bruce]

Hi Gordon,

>> BTW, wouldn't it make sense to cache on the url including arguments instead of just the file name?

yes, probably. I will look into that at some point. the cache was created originally as a "shared memory store" so that multiple requests for the same static file consumed (a lot) less memory. So the "request" is not cached at the moment, only the file.

For now turn it off on your side - the performance hit is very small - possibly the best longer-term approach is for me to make it an expression like some of the other settings, so it can be turned on and off at runtime.

chers
Bruce