Closed xtitter closed 8 years ago
yeah, I agree, although in theory that's exactly what browsers ought to be doing themselves in the first place...
Can't we just set HTTP headers on snap.html or each file to send a no-cache message.
Michael Ball http://www.michaelballphoto.com Photos & iPhone Apps!
On Wed, Nov 6, 2013 at 2:07 AM, Jens Mönig notifications@github.com wrote:
yeah, I agree, although in theory that's exactly what browsers ought to be doing themselves in the first place...
— Reply to this email directly or view it on GitHubhttps://github.com/jmoenig/Snap--Build-Your-Own-Blocks/issues/220#issuecomment-27859225 .
This is being worked on -- I just got a flurry of emails about it.
This is being worked on -- I just got a flurry of emails about it.
From github or something else? (unless you meant our other discussion thread?)
Yeah, maybe about bjc, but you're supposedly solving this problem.
Hah, ok. Yes, I didn't know if you meant i was or someone else was. But eventually I should have everything working.
Closing since we have #346
Maybe many of the problems users see are due to non-refreshed browser caches. Snap should determine a 'latest version' from snap.berkeley.edu and compare it against the version that is being run, requesting that the user refresh the browser if they aren't the same.