On 11/8/2014, 8:31 AM, Ethan Lish wrote:
How can one control the cache or force the reload of a remote stack?
Using the algorithm defined in this lesson
http://lessons.runrev.com/m/4071/l/78702-opening-a-stack-from-the-server
When the client is restarted it does not reload the changed stack from the
server
My project was having the same problem and it turns out that the user's
ISP was caching the files. If you wait long enough (usually 24 hours,
but it varies by company) their cache is cleared and you get the updated
file the next time you retrieve it.
You might be able to add a timestamp to the request, which makes it look
like a different file to the cache:
put "http://www.domain.com/file.jpg?timestamp="; & the seconds into tURL
go stack url tURL
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
![http://www.domain.com/file.jpg?timestamp="](http://www.domain.com/file.jpg?timestamp="){kind=link}