From the FAQ : "Usually, the weather is delivered to YoWindow in 10 - 40 minutes after the moment it was observed at the station."
My mostest favoritest part of the FAQ is the word "Usually..." That usually means "sometimes it do - BUT - sometimes it don't."
Sounds almost like the FAQ is saying that there's an adaptive relationship between the server/station and all the YoWindow computers who have chosen that "station" and are online at any given point; rather than each computer's application sends out a request and then the server acknowledges accordingly.
What I just now did was 1) read the temperature in the tray area; 2) since you cannot get to the F5 action from the tray area display's context menu, I launched the window, which stated "Observed 1 h 42 m ago"; 3) I manually pressed F5 while the YoWndow was in focus; and 4) the information changed/updated to "Observed 3 m ago".
My original post was contemplating control over the time-increments at which the application [on MY computer] sends out a request [to MY location's weather-server] for an update... Maybe the information would not have changed; but at the point of the update transaction-attempt, the information would be current on the chosen server. Or, perhaps, no update request could be acknowledged by the server for any one or combination of the plausible events listed in your referenced FAQ item. While "F5" or "Menu bar | View | Update weather" is normally available with my/your/YoWindow's interface, "It would be nice..." while running YoWindow constantly [from the SysTray Notification Area of my taskbar] to have a little control over the program's update intervals - both from an observational standpoint as well as from a diagnostic standpoint [if needed, to determine if there is any connectivity problems]. FYI, IN MY CASE, I run certain monitoring applications/utilities all the time - perpetually on-line - such as an Internet radio station [gives me an audible verification of my connectivity... while they MIGHT have some sort of issue from time-to-time]; an eMail checker/washer/filter; and an instant messaging application... Add a weather-monitoring utility, and if there be a connectivity issue on my end, it might be apparent by quickly scanning the other utilities to determine the likely source.
In the case of YoWindow's FAQ, "Usually... 10 - 40 minutes" might suggest server-side control over the delivering of the information; juxtaposed to my utilization's requesting the updated information and the server acknowledging.
Yes, well constructed FAQ's are always nice to read before posting a request in the "Suggestions" topic area... It's almost like saying "Oh, you CAN make a suggestion [or a request]... BUT, we've probably already got an FAQ preempting that!
Thanks again for your thoughtful considerations.
Sincerely yours,
Kaoz
)