Droptop used a trunc of current minute divided by 20 with an OnChangeAction to trigger the webparser update. Eg. at 0 minutes, 20 minutes, and 40 minutes of every hour.There is something I don't understand from their complaint though: they said the calls were at precisely the same time, 3 times per hour. But here's the thing: it's not practically possible that all calls were at precisely the same time given that it would be an unheard coincidence that all users loaded their skins in unison, unless one of these checks out:
- the skins were used in a 4.000 computers network, where the supposed server somehow triggered all skins to load at the same time
- the skins used Time measures instead of UpdateDivider to retrieve data at the 00th, 20th and 40th minute every hour, instead of at every 20 minutes regardless of the actual time
You probably don't know the former, but on the latter, did you by any chance used that approach to get data from the site? Just curious...
Time measure is used as WebParser would otherwise attempt to update every time the skin is refreshed. Instead the OnChangeAction opens a separate ini that deactivates itself once the parsing is complete. Alternatively I could look into using a trunc of a Counter measure so that users should theoretically parse at all different times of the day.
Statistics: Posted by Cariboudjan — Today, 1:33 pm