Page 1 of 1
Revolution Browser Instance caching?
Posted: Fri Oct 17, 2008 11:02 pm
by hsthompson
I'm familiar with Flash, but not with Revolution. Our Rev programmer is busy, so I'm trying to troubleshoot this caching issue we've been having with some installed kiosks.
Set up:
Apple Leopard 10.5.2
Runtime Revolution
Adobe Flash 9.x
Scenario:
1. App containing Revolution browser instance loads .swf file.
2. .swf loads data from file via LoadVariables, and displays it in some text fields.
3. .swf or data file is updated.
4. Revolution browser instance is quit and relaunched, but shows both the old .swf file, and the old data from the data file.
We need to find a fix that doesn't require human intervention.
Posted: Sat Oct 18, 2008 8:31 am
by Mark
Hi hsthompson,
I doubt that this is a caching problem. What exactly does step 3 consist of?
Best,
Mark
Posted: Mon Oct 20, 2008 10:06 pm
by hsthompson
Hi Mark. We think it's a caching problem because using Onyx to clear the user caches (we've tried just clearing the Internet caches, without success), and then rebooting, allows the data to reflect updates.
Step 3, means changing the content of the data file (URL encoded text) that's loaded by the SWF, and/or changing and re-exporting the SWF file loaded into the browser instance.
Posted: Mon Oct 20, 2008 10:34 pm
by Mark
Dear hsthompson,
Alright, it might be a caching problem, but it is not clear that Revolution has got anything to do with it.
Your explanation is far from clear. Does the data file contain URL encoded text? How is that relevant? Exporting a flash file has nothing to do with Revolution.
When and how are you reloading the htmlText of the browser instance?
Best,
Mark
Posted: Mon Oct 20, 2008 11:02 pm
by hsthompson
I don't know what "htmlText" refers to. As far as I know, the SWF is being loaded into the browser instance directly (unless there's an HTML file being created on the fly somewhere). As I'd said, I'm not Revolution savvy.
The data file is a plain text file with URL encoded data (e.g. variable1=value1&variable2=value2).
Re: the exporting of the SWF. The browser instance points to a given path to a SWF file. Under Leopard (as opposed to Tiger, where this worked more reliably) the app with the browser instance, even when repeatedly relaunched, continues to display the old SWF and/or the old data loaded by the SWF.
Posted: Tue Oct 28, 2008 6:27 pm
by hsthompson
The problem is solved; it was a caching issue.
The relevant caches under Leopard are located in two randomly-named directories at the path:
/private/var/folders
More detailed information available here:
http://rixstep.com/2/20080810,00.shtml