Aha... now I see, thanks a lot for clarification. I thought that the 10min means max 1 request /10 min. So is there any limit as to how many different locations you are allowed to load? Assuming you use say 1h caching for each?
Well I did the dynamic and test it by my self and try to caching them simultaeneously, as I check its cache loads, it only consumes 2mb total similar to my WU historical data which uses 1-2 mb of cache per hr, so I think it would be a piece of cake to yr.No if viewers caching their data at the same time together since the sample Ive shown you actually when I check its cache files its totally 2 mb per cache and steady in that sized whenever I load all of his diff locations together, it means yr.No has automatic clear cache or overwrites the cache file on the folder since it only uses note more than 2mb. Now im uploading the files ived made now and made it a total of 16MB after my setup with this
I am not sure I understand your point, let me explain:
The Leuven scripts (1) read the xml forecast data (2) convert them to the units used on the website (3) convert icons (4-8) a.s.o. and (9) save the resulting php array into the ./cache/ folder. Subsequent requests for the same data start with reading the arrays, on slower webservers this will easily remove 0.5 - 1 second from the response times especially on busier hours.
The script using the yrno forecast needs two different xml files which result in two small cache files of 22 and 26 KB.
Most Leuven-forecast scripts replace the cache every two hours and / or check if a new forecast is available:
This can be checked in the generated html
<!-- module yrnoGenerateHtml.php (32): loading ./wsyrnofct/yrnoCreateArr.php -->
<!-- module yrnoCreateArr.php ==== version: 3.20 2015-08-25 -->
<!-- module yrnoCreateArr.php (194):./cache/yrnoCreateArr.php-en-United_Statesxxxxx-fmhininhg loaded from cache
next-update at 2017-04-28T03:00:00-05:00 (1493366400)
it is now 2017-04-28T01:40:54-05:00 (1493361654) -->
<!-- module yrnoGenerateHtml.php (370):
temp max: 63 temp min: 37 temp step: 10 temp max: 80 temp min: 10 icon: 75
rain max: 3.6 rain step: 0.6
baro max: 32 baro min: 28.5
wind max: 48 wind step: 8
-->
<!-- module yrnoGenerateHtml.php (592): loading ./wsyrnofct/yrnoCreateDetailArr.php -->
<!-- module yrnoCreateDetailArr.php ==== version: 3.20 2015-08-02 -->
<!-- module yrnoCreateDetailArr.php (174): ./cache/yrnoCreateDetailArr.php-en-United_Statesxxxxxx-fmhininhg loaded from cache
next-update at 2017-04-28T03:00:00-05:00 (1493366400)
it is now 2017-04-28T01:40:54-05:00 (1493361654) -->
<!-- start output ws_yrno_page -->
===
I think that there is no use to adapt the scripts for caching the way they are built now.
I am writing a new version of all forecast scripts this summer (after NWS cut-over) so if you have ideas for improvement, please let me know.
Wim