Re: Where are these stacks being cached?

2014-08-14 Thread Peter W A Wood
Is the stack being cached by Amazon - 
http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Expiration.html

Peter

J. Landman Gay jac...@hyperactivesw.com wrote:

Thanks for leaving Nabble to get this info here Shawn. I can have my 
client try that. We did discuss DNS issues and decided it probably 
wouldn't apply, because the DNS always resolves to Amazon and that 
doesn't change (though AWS does redirect to lots of different servers.)

I'm still not sure how an old DNS lookup could download a file that 
doesn't exist on the server though. None of the stacks are ever saved to 
disk, they are always in RAM only, so they have to be coming from the 
internet somewhere.


On 8/13/2014, 5:07 PM, Shawn Blc wrote:
 Tried to post on the nabble revolution list, but so far it hasn't been
 accepted (ok, but odd).   So I'll post here.

 ---
 I'm sure you've tried the following, but if you haven't:


 osx mavericks
 
 dscacheutil -flushcache
 sudo killall -HUP mDNSResponder

 or

 windows 7
 
 ipconfig /flushdns
 --




 On Wed, Aug 13, 2014 at 5:03 PM, Mark Wieder mwie...@ahsoftware.net wrote:

 Jacque-

 Try clearing the browser cache on those machines using browser-specific
 instructions, each one different. My guess is the browser has cached the
 old version and is helpfully saving the user from having to download again.

 --
   Mark Wieder
   ahsoftw...@gmail.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

 ___
 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



-- 
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
___
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

Re: Where are these stacks being cached?

2014-08-14 Thread J. Landman Gay

On 8/14/2014, 1:28 AM, Peter W A Wood wrote:

Is the stack being cached by Amazon 
-http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Expiration.html



Aha. Yes, it very well could be. I just knew an old copy had to be 
stashed somewhere.


This may be coupled with the DNS issue too; an old URL might be pointing 
to a cached copy. I haven't quite worked out exactly how that would 
happen but it sounds right.


Thank you.

--
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


Where are these stacks being cached?

2014-08-13 Thread J. Landman Gay
In today's episode, our hero has uploaded new copies of revised stacks 
to Amazon Web Services. We have verified that no older copies exist 
there anywhere, including on all edge servers.


Back at home, a LC splash app retrieves these stacks from the server. 
Much of the time an older version of the stack is always retrieved. The 
problem is dependent on the computer. If the computer has opened that 
stack before, the old version is shown. On a computer that has never 
opened the stack before, the new version is shown.


This would be normal if it were all in the same session, but the problem 
persists after restarting the app, restarting the computer, and even 
after waiting several hours, restarting the computer, and then 
restarting the app. Yesterday it took perhaps 8 hours before the updated 
stacks could be retrieved on a computer that had loaded the stack 
previously.


There would appear to be a cache somewhere that is not updating often 
enough. Since it is computer specific, it must be based on MAC address, 
but we can't figure out where. Does the computer cache files even if 
they aren't web browser temp files? How about the local router? How 
about the cable broadband router? It seems unlikely that AWS would send 
a cached version, since all the requests are coming from the same local 
LAN and I believe AWS would only see the outside IP, not the MAC 
address. But maybe that's wrong?


Anyone know where the old stacks are being stored? We want only the 
latest versions to load as soon as they are made available.


--
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


Re: Where are these stacks being cached?

2014-08-13 Thread Mark Wieder
Jacque-

Try clearing the browser cache on those machines using browser-specific
instructions, each one different. My guess is the browser has cached the
old version and is helpfully saving the user from having to download again.

-- 
 Mark Wieder
 ahsoftw...@gmail.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


Re: Where are these stacks being cached?

2014-08-13 Thread Shawn Blc
Tried to post on the nabble revolution list, but so far it hasn't been
accepted (ok, but odd).   So I'll post here.

---
I'm sure you've tried the following, but if you haven't:


osx mavericks

dscacheutil -flushcache
sudo killall -HUP mDNSResponder

or

windows 7

ipconfig /flushdns
--




On Wed, Aug 13, 2014 at 5:03 PM, Mark Wieder mwie...@ahsoftware.net wrote:

 Jacque-

 Try clearing the browser cache on those machines using browser-specific
 instructions, each one different. My guess is the browser has cached the
 old version and is helpfully saving the user from having to download again.

 --
  Mark Wieder
  ahsoftw...@gmail.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

___
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


Re: Where are these stacks being cached?

2014-08-13 Thread J. Landman Gay

On 8/13/2014, 5:03 PM, Mark Wieder wrote:

Jacque-

Try clearing the browser cache on those machines using browser-specific
instructions, each one different. My guess is the browser has cached the
old version and is helpfully saving the user from having to download again.



There are no browser objects in the stacks anywhere, but just in case, 
we did try that. We aren't loading anything related to web pages, so I 
didn't think it would apply. I was right. No go.


Another thing we tried was taking the computer that had already seen the 
stacks and connecting it to a different network on a different broadband 
router (to force a change in the IP.) Same deal; old stack loaded.


It's really weird.

--
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


Re: Where are these stacks being cached?

2014-08-13 Thread J. Landman Gay
Thanks for leaving Nabble to get this info here Shawn. I can have my 
client try that. We did discuss DNS issues and decided it probably 
wouldn't apply, because the DNS always resolves to Amazon and that 
doesn't change (though AWS does redirect to lots of different servers.)


I'm still not sure how an old DNS lookup could download a file that 
doesn't exist on the server though. None of the stacks are ever saved to 
disk, they are always in RAM only, so they have to be coming from the 
internet somewhere.



On 8/13/2014, 5:07 PM, Shawn Blc wrote:

Tried to post on the nabble revolution list, but so far it hasn't been
accepted (ok, but odd).   So I'll post here.

---
I'm sure you've tried the following, but if you haven't:


osx mavericks

dscacheutil -flushcache
sudo killall -HUP mDNSResponder

or

windows 7

ipconfig /flushdns
--




On Wed, Aug 13, 2014 at 5:03 PM, Mark Wieder mwie...@ahsoftware.net wrote:


Jacque-

Try clearing the browser cache on those machines using browser-specific
instructions, each one different. My guess is the browser has cached the
old version and is helpfully saving the user from having to download again.

--
  Mark Wieder
  ahsoftw...@gmail.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


___
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




--
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


Re: Where are these stacks being cached?

2014-08-13 Thread Mark Wieder
Jacque-

 Thanks for leaving Nabble to get this info here Shawn. I can have my 
 client try that. We did discuss DNS issues and decided it probably 
 wouldn't apply, because the DNS always resolves to Amazon and that 
 doesn't change (though AWS does redirect to lots of different servers.)

I'm not sure about that. If AWS needs to respawn the server the resolved ip
address isn't guaranteed to be the same. In fact, in our experience it's
always different after a reboot of the server. YMMV.

-- 
 Mark Wieder
 ahsoftw...@gmail.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


Re: Where are these stacks being cached?

2014-08-13 Thread Mark Talluto

On Aug 13, 2014, at 2:01 PM, J. Landman Gay jac...@hyperactivesw.com wrote:

 Anyone know where the old stacks are being stored? We want only the latest 
 versions to load as soon as they are made available.

Is is possible the client is behind a proxy server?  

Sometime adding this to your url links:  [linkHere]  ?x=  the seconds into 
tURLtoFile

Will help you force the file to skip the cached version on the proxy server and 
download it again from the true source.


Best regards,

Mark Talluto
CanelaSoftware.com
LiveCloud.io






___
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


Re: Where are these stacks being cached?

2014-08-13 Thread Stephen MacLean
Hi Jacque,

Are you using “load URL” to call those stacks to download?

It will cache the what was called and I had problems getting it to release and 
get fresh data, etc.

hth,

Steve MacLean

On Aug 13, 2014, at 5:01 PM, J. Landman Gay jac...@hyperactivesw.com wrote:

 In today's episode, our hero has uploaded new copies of revised stacks to 
 Amazon Web Services. We have verified that no older copies exist there 
 anywhere, including on all edge servers.
 
 Back at home, a LC splash app retrieves these stacks from the server. Much of 
 the time an older version of the stack is always retrieved. The problem is 
 dependent on the computer. If the computer has opened that stack before, the 
 old version is shown. On a computer that has never opened the stack before, 
 the new version is shown.
 
 This would be normal if it were all in the same session, but the problem 
 persists after restarting the app, restarting the computer, and even after 
 waiting several hours, restarting the computer, and then restarting the app. 
 Yesterday it took perhaps 8 hours before the updated stacks could be 
 retrieved on a computer that had loaded the stack previously.
 
 There would appear to be a cache somewhere that is not updating often enough. 
 Since it is computer specific, it must be based on MAC address, but we can't 
 figure out where. Does the computer cache files even if they aren't web 
 browser temp files? How about the local router? How about the cable broadband 
 router? It seems unlikely that AWS would send a cached version, since all the 
 requests are coming from the same local LAN and I believe AWS would only see 
 the outside IP, not the MAC address. But maybe that's wrong?
 
 Anyone know where the old stacks are being stored? We want only the latest 
 versions to load as soon as they are made available.
 
 -- 
 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



___
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


Re: Where are these stacks being cached?

2014-08-13 Thread J. Landman Gay

Lumping some answers together:


Is is possible the client is behind a proxy server?


It will be possible eventually but right now nobody is.


Sometime adding this to your url links:  [linkHere]  ?x=  the seconds

 into tURLtoFile


Will help you force the file to skip the cached version on the proxy server


In this case the URL is a huge, long signed URL in AWS secure format. If 
I alter it at all, AWS will reject it. :(



Are you using “load URL” to call those stacks to download?


No, I'm using go url followed by a bunch of AWS gibberish.


If AWS needs to respawn the server the resolved ip
address isn't guaranteed to be the same.


Okay, didn't know that. So tomorrow we'll try the DNS thing that's been 
suggested and see what happens. If that works, it's only a data point, 
because we can't ask the users to run terminal commands to use the app. 
In that case I'm not sure what to do, but I'll wait until we know that's 
the problem first.


--
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