[Xerte-dev] Re: Browser caching and problems it causes with each update

[Pat L (pgogy)]

3 is what wp does and it makes sense to me
Do css as well?

-------- Original message --------
From: Tom Reijnders <reijnders at tor.nl> 
Date: 20/02/2016  12:18  (GMT+00:00) 
To: For Xerte technical developers <xerte-dev at lists.nottingham.ac.uk> 
Subject: [Xerte-dev] Browser caching and problems it causes with each update 

Hi,

I've had several instances where we had a sudden increase of support 
calls after installing an update of XOT (i.e. from 3.0 to 3.1)

Most of those were due to caching issues. i.e. new modelfiles were used 
against a previous cached version of xenith.js

There are several solutions to this:

1. At a timestamp in the url that loads xenth.js , ie 
src="xenith.js?_=<?php echo $timestamp;?>" or similar

The drawback of course is that xenith.js (and similar files) are not 
cached anymore, increasing the time needed to load an LO

2. Add a version to the filename of xenith.js, i.e. everytime something 
changes in xenith.js, change the version.

This is the approach used by a lot of javascript libraries, cf. jQuery. 
But it it's painfull, and errorprone (or we have to have a build process).

3. An interesting variation could be the combination of 1. and 2.

We have a version string maintained in the file version.txt in the root 
folder of the installation. This file is automatically updated when 
publishing zips for the community websites. We could add 
?version='<contents of version.txt>' to all the files we want to reload 
after a new release, such as xenith.js

Tests show that this works fine ans as expected. I would like to 
implement 3.

Any objections, remarks, other solutions?

Tom


-- 
--

Tom Reijnders
TOR Informatica
Chopinlaan 27
5242HM Rosmalen
Tel: 073 5226191
Fax: 073 5226196


_______________________________________________
Xerte-dev mailing list
Xerte-dev at lists.nottingham.ac.uk
http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev




This message and any attachment are intended solely for the addressee
and may contain confidential information. If you have received this
message in error, please send it back to me, and immediately delete it. 

Please do not use, copy or disclose the information contained in this
message or in any attachment.  Any views or opinions expressed by the
author of this email do not necessarily reflect the views of the
University of Nottingham.

This message has been checked for viruses but the contents of an
attachment may still contain software viruses which could damage your
computer system, you are advised to perform your own checks. Email
communications with the University of Nottingham may be monitored as
permitted by UK legislation.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nottingham.ac.uk/pipermail/xerte-dev/attachments/20160220/d01b9f02/attachment.html>