<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>3 is what wp does and it makes sense to me<div><br><div dir="auto">Do css as well?</div></div><br><br>-------- Original message --------<br>From: Tom Reijnders <reijnders@tor.nl> <br>Date: 20/02/2016 12:18 (GMT+00:00) <br>To: For Xerte technical developers <xerte-dev@lists.nottingham.ac.uk> <br>Subject: [Xerte-dev] Browser caching and problems it causes with each update <br><br>Hi,<br><br>I've had several instances where we had a sudden increase of support <br>calls after installing an update of XOT (i.e. from 3.0 to 3.1)<br><br>Most of those were due to caching issues. i.e. new modelfiles were used <br>against a previous cached version of xenith.js<br><br>There are several solutions to this:<br><br>1. At a timestamp in the url that loads xenth.js , ie <br>src="xenith.js?_=<?php echo $timestamp;?>" or similar<br><br>The drawback of course is that xenith.js (and similar files) are not <br>cached anymore, increasing the time needed to load an LO<br><br>2. Add a version to the filename of xenith.js, i.e. everytime something <br>changes in xenith.js, change the version.<br><br>This is the approach used by a lot of javascript libraries, cf. jQuery. <br>But it it's painfull, and errorprone (or we have to have a build process).<br><br>3. An interesting variation could be the combination of 1. and 2.<br><br>We have a version string maintained in the file version.txt in the root <br>folder of the installation. This file is automatically updated when <br>publishing zips for the community websites. We could add <br>?version='<contents of version.txt>' to all the files we want to reload <br>after a new release, such as xenith.js<br><br>Tests show that this works fine ans as expected. I would like to <br>implement 3.<br><br>Any objections, remarks, other solutions?<br><br>Tom<br><br><br>-- <br>--<br><br>Tom Reijnders<br>TOR Informatica<br>Chopinlaan 27<br>5242HM Rosmalen<br>Tel: 073 5226191<br>Fax: 073 5226196<br><br><br>_______________________________________________<br>Xerte-dev mailing list<br>Xerte-dev@lists.nottingham.ac.uk<br>http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev<br><br><br><br><br>This message and any attachment are intended solely for the addressee<br>and may contain confidential information. If you have received this<br>message in error, please send it back to me, and immediately delete it. <br><br>Please do not use, copy or disclose the information contained in this<br>message or in any attachment. Any views or opinions expressed by the<br>author of this email do not necessarily reflect the views of the<br>University of Nottingham.<br><br>This message has been checked for viruses but the contents of an<br>attachment may still contain software viruses which could damage your<br>computer system, you are advised to perform your own checks. Email<br>communications with the University of Nottingham may be monitored as<br>permitted by UK legislation.<br><br></body></html>