I've been building a graphical front end controlled via a text log file that
is frequently updated by a running process. The log file and web server are
on the same unix box. I read the text log file using LoadVars. All well and
good.
The flash code reads the log file, extracts pertinent data and runs
animations accordingly. For the most part it works well - reading from a
static log file - no problem.
In practice, the log file is not static and is being continually refreshed
by another process that changes it's content. The flash code repeatedly
re-reads the changing log file and the whole thing will start again,
repeating as required.
Now to the point: Since the flash front end runs in a browser, I realise
that supplying a url to read the logfile from using Loadvars would be prone
to caching in the browser and adding a changing parameter in the file url
would deal with that. In my case, rather than use a url I've specified the
logfile location as a relative path from the swf, therby avoiding sandbox
restrictions.
Using this technique (a relative path), is the file read prone to be cached
by the browser?
If so, is there any way to defeat the caching when using a relative file
path (since you can't include a changing parameter in what looks like a
local file)?
If this file is being cached, I guess I'll have no choice but to use a url,
cache killer parameter and a policy file.
Thanks,
Paul
_______________________________________________
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
