Jim, I agree.jmcmurry wrote: Hmmm, perhaps the minimum interval could be set in the xml thus leaving ultimate control with the xml creator/host?
- Jim
A current conditions "refresh interval" (reload interval) in the XML for when its a PWS is a better idea.
Maybe also introduce a "max updates" allowed parameter after which the "refresh" (F5) button is activated.
Let the PWS owner then decide how much bandwidth he's prepared to sacrifice.
When it's updated from NOAA it should do so only every 30 minutes seeing that the METAR's are at most updated at this frequency.
Mine for instance, FAJS, is only refreshed every hour and in some cases it can go up to 2 hours.
Here in Africa some METAR stations only bother updating when they have a plane arriving, otherwise not.
And most of the time most of the METAR's are stale.
Par, I don't know what your refresh interval is at this time, but if it's heavy then that's maybe why they have pulled the plug on you.
My suggestion is to download the METAR/TAF once at startup and then 5 minutes after the hour/half hour.
If the F5 refresh is there to prevent the above from happening then I think the users might be hitting it too often.
Maybe you should disable the F5 function, if the METAR/TAF has been refreshed successfully, up to the next
expected METAR update i.e. 5 minutes after the hour/half hour. AMD (amended), COR (corrected) and CNL (cancelled)
METAR's should be ignored seeing that you're only dealing with the general public here.
That should prevent Yowindow from clobbering NOAA.