Remote stack

Ethan Lish ethanlish at gmail.com
Sun Nov 9 10:36:25 EST 2014


Excellent!  This did the trick. Thanks 


E


—
Ethan at Lish.net240.876.1389

On Sat, Nov 8, 2014 at 7:43 PM, Mike Bonner <bonnmike at gmail.com> wrote:

> Like the timestamp, you can just tack on a # and the milliseconds to each
> request.  http://whatever.url.com/mystack.livecode#134513461
> Same theory, it always looks like a new hit due to the #1235124561 (At
> least I think it works with just a figmentary anchor)
> On Sat, Nov 8, 2014 at 12:17 PM, J. Landman Gay <jacque at hyperactivesw.com>
> wrote:
>> 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         |     jacque at hyperactivesw.com
>> HyperActive Software           |     http://www.hyperactivesw.com
>>
>>
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


More information about the use-livecode mailing list