Hi! We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
But as we’re losing ad-revenue from this then why not make a donation towards website running costs?. Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!
That just clears your IP name cache (which probably only lives for around 15 minutes, anyway).
As it's unlikely that would be the problem, or changing, doesn't seem that relevant.
The browser tends to be caching pages and object, but as others have said, it's most likely to be ISPs that are caching pages and downloads that is the issue.
Agreed although you local DNS can live for up to 24 hours (not just 15 minutes) so sometimes it is worth clearing it.
Your local hostname cache (ie on the client machine) will live for around 15 minutes, unless the record keeps being requested, in which case the TTL from the DNS record will likely apply.
For DNS caching nameservers, the TTL for the record / zone will almost certainly apply.
But for your hostname cache locally (which is what ipconfig /flushdns would flush) will only live around 15 minutes, if the name is just looked up once, or quite infrequently.
The local hostname cache is only transient, isn't there to totally follow the caching employed by DNS nameservers, and was only included on windows OSs from Windows 2000 onwards (before that, only netBIOS hostnames were cached).
That just clears your IP name cache (which probably only lives for around 15 minutes, anyway).
As it's unlikely that would be the problem, or changing, doesn't seem that relevant.
The browser tends to be caching pages and object, but as others have said, it's most likely to be ISPs that are caching pages and downloads that is the issue.
Agreed although you local DNS can live for up to 24 hours (not just 15 minutes) so sometimes it is worth clearing it.
Your local hostname cache (ie on the client machine) will live for around 15 minutes, unless the record keeps being requested, in which case the TTL from the DNS record will likely apply.
For DNS caching nameservers, the TTL for the record / zone will almost certainly apply.
But for your hostname cache locally (which is what ipconfig /flushdns would flush) will only live around 15 minutes, if the name is just looked up once, or quite infrequently.
The local hostname cache is only transient, isn't there to totally follow the caching employed by DNS nameservers, and was only included on windows OSs from Windows 2000 onwards (before that, only netBIOS hostnames were cached).
Good old Windows!!! _________________ Garmin i3
Firmware 3.4
Well I cleared cache its now much later and I have downloaded several more times and still ;- Beta version expired
Any other sugestions to try
i think he means the isp's cache. i also have problems with freeserve users downloading files from my site - freeserve (among others) cache sites to make downloading faster but can cause problems when their cache is not updated...
i'm sure someone can email you the file! however, i'm at work and can't download it
MaFt
Ash, would it be worth you using a service such as Save File to host the files so to avoid this caching issue? http://www.savefile.com _________________ Garmin i3
Firmware 3.4
That just clears your IP name cache (which probably only lives for around 15 minutes, anyway).
As it's unlikely that would be the problem, or changing, doesn't seem that relevant.
The browser tends to be caching pages and object, but as others have said, it's most likely to be ISPs that are caching pages and downloads that is the issue.
Agreed although you local DNS can live for up to 24 hours (not just 15 minutes) so sometimes it is worth clearing it.
Your local hostname cache (ie on the client machine) will live for around 15 minutes, unless the record keeps being requested, in which case the TTL from the DNS record will likely apply.
For DNS caching nameservers, the TTL for the record / zone will almost certainly apply.
But for your hostname cache locally (which is what ipconfig /flushdns would flush) will only live around 15 minutes, if the name is just looked up once, or quite infrequently.
The local hostname cache is only transient, isn't there to totally follow the caching employed by DNS nameservers, and was only included on windows OSs from Windows 2000 onwards (before that, only netBIOS hostnames were cached).
I bow yo your superior knowledge sir.
I have just checked the MS KB and it appears that negative DNS entries are only cached for a maximum of 5 minutes as well. You learn something everyday. _________________ Garmin i3
Firmware 3.4
Your local hostname cache (ie on the client machine) will live for around 15 minutes, unless the record keeps being requested, in which case the TTL from the DNS record will likely apply.
For DNS caching nameservers, the TTL for the record / zone will almost certainly apply.
But for your hostname cache locally (which is what ipconfig /flushdns would flush) will only live around 15 minutes, if the name is just looked up once, or quite infrequently.
The local hostname cache is only transient, isn't there to totally follow the caching employed by DNS nameservers, and was only included on windows OSs from Windows 2000 onwards (before that, only netBIOS hostnames were cached).
I bow yo your superior knowledge sir.
I have just checked the MS KB and it appears that negative DNS entries are only cached for a maximum of 5 minutes as well. You learn something everyday.
Well client side caching is never likely to be much of a problem - negative caching isn't really that much of a special case - hostname caches still tend to observe normal rules, and assuming nothing populating / polluting cache, will observe TTLs.
But it's a red herring, anyway - it's highly unlikely any name caching (at any point in the chain) is likely to be causing any problems - especially given the context of this issue with the file downloads - unless the names / details change much at source, anyway.
POI loader stops responding everytime I try to load up Ash's files.
If I revert to the standard pocketgps camera file it works OK.
What am I doing wrong?
POI loader stops responding everytime I try to load up Ash's files.
If I revert to the standard pocketgps camera file it works OK.
What am I doing wrong?
When you say stops responding, I wouldn't necessarily worry - I don't personally use Ash's app, I use a similar app written by cbrom, which produces much the same in output gpx files.
When I load them using POIloader, POIloader will hang for up to five minutes whilst it's doing it's thang. Then I hear the i3 bleep, as it's effectively rebooted, and it's done. During the period when POIloader "hangs" though - the OS sees it as not responding.
So you may not necessarily have a problem, perhaps you just need to be a bit patient and let it run for a bit longer.
Joined: Aug 31, 2005 Posts: 15155 Location: Bradford, West Yorkshire
Posted: Fri Sep 29, 2006 2:11 pm Post subject:
the gpx files are a LOT bigger than the csv files so takes poiloader a lot longer to process them. hence the delay as lester pointed out.
also, ash, i uploaded latest camera's t'other night yet your app keeps telling me updates are ready to install... this has already ben done! anyway to tell it that i've already actually installed them and to wait until there IS actually a new release?
the gpx files are a LOT bigger than the csv files so takes poiloader a lot longer to process them. hence the delay as lester pointed out.
also, ash, i uploaded latest camera's t'other night yet your app keeps telling me updates are ready to install... this has already ben done! anyway to tell it that i've already actually installed them and to wait until there IS actually a new release?
MaFt
Have you uploaded your POI loader? Ash's new app only works with latest 2 or 3 versions. _________________ Garmin i3
Firmware 3.4
Joined: Aug 31, 2005 Posts: 15155 Location: Bradford, West Yorkshire
Posted: Mon Oct 02, 2006 2:24 pm Post subject:
trevf wrote:
MaFt wrote:
the gpx files are a LOT bigger than the csv files so takes poiloader a lot longer to process them. hence the delay as lester pointed out.
also, ash, i uploaded latest camera's t'other night yet your app keeps telling me updates are ready to install... this has already ben done! anyway to tell it that i've already actually installed them and to wait until there IS actually a new release?
MaFt
Have you uploaded your POI loader? Ash's new app only works with latest 2 or 3 versions.
Joined: 26/08/2003 15:43:37 Posts: 386 Location: Southampton, UK
Posted: Mon Oct 02, 2006 2:57 pm Post subject:
Well after all the kerfuffle to download Ash's application it works much better than before for me .
After the conversion I ran the latest version of POI loader and was getting out of my seat to make a coffee as it tended to upload to my 2720 at quite a slow rate ,when blow me it was done ,just like that and it also displays on the 2720 better as well. I used to get the camera No # speed but now it displays a caution banner and speed .
Thanks Ash :D _________________ Asus Zenfone 2 twin sim, Garmin Zumo 550, 660 and pocketgps speed camera database
I keep on learning but they invent new things faster ,How do I keep up ?
Posted: Today Post subject: Pocket GPS Advertising
We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
Have you considered making a donation towards website running costs?. Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!
Hi! We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
But as we’re losing ad-revenue from this then why not make a donation towards website running costs?. Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!