Your approach will poll every possible severs by every clients in the world so we will lose the random load-balancer advantage, there is no need for this when there is no problem. While my approach will not.
I will check the LastUpdate.log only on the already selected random mirror and then only switch to another one when needed.
The problem with this is that you don't know the status of a server until you can compare it to the others. If you get "2018-08-10" back, does that mean you discard it (because it is not today)? Or does that mean there was no update today and that server does contain the latest version? Or perhaps that your box is in a timezone so for away from Willy's timezone that there is a day difference?
You can also not compare it to something you have locally. If your box has been in deep standby for a week, the fact that a servers reports a date more recent than your last download doesn't say anything about how current the data on the server is.
Polling the servers to check the status isn't a problem, it is not the number of hits, it is the volume per month that is a challenge for those servers.
1) I say that we must still consider the server if it is in a 2 days difference slot between the local STB date and the LastUpdate.log, this will cover the world timezone. Since in the world we only have 1 day difference, that's where the 2 days came from.
2) If Willy upload has a problem to upload to every server that last 3 days, then your LastUpdate.log on ALL the servers will be the same (exemple 2018-08-07) and then which conclusion can you take today we are the 2018-08-11, if you didn't check the local date of the STB then you will download and process an obsolete data file, so same as today.
3) Timezone difference is always between +12H -12H from you position on earth, so always in MAX 1 day difference (the earth turn on itself in 24H). So 2 days to compare date is nice.
4) I never take into consideration the last download date in the brainstorm, this information is useless
5) Using a STB which is not at the right date and time to download EPG is totally useless... since you will upload in memory EPG datas that are set for the right date and time for the program. If your STB is still in the past you will NEVER saw the EPG informations. So to use EPG your STB has to be at the right date and time.
(Remark: that's why OpenPLi should implement by default in its image the SystemTime plugin setup to use NTP server instead of TP time; so when starting a STB even without antenna connected the STB will always be at the right time). And if people use the EPGimport the box is connected to the Internet, people that are not connected to the Internet then use TP time and don't use EPGimport.
So you need to compare with the local STB date with the LastUpdate.log and not trust the server date in this file since you can't conclude nothing from it about the current real life date. Another argument is that you cannot unscramble channel when the date and time is not correct since it is also timebased. So you really can assume that the STB is at the right time.
Pr2
NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.
If you think that my answer helps you, you can press the up arrow in bottom right of the answer.
Wanna help with OpenPLi Translation? Please read our Wiki Information for translators
Sat: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C) & Duo 4K: 2*DVB-S2X + DVB-C (FBC)
AB-Com: PULSe 4K 1*DVB-S2X (+ DVB-C/T/T2)
Edision OS Mio 4K: 1*DVB-S2X + 1*DVB-C/T/T2