A few minutes is a bit too much for a load time error, but yeah, WebParser can get hung up when abused frequently - which leads me to another point I was about to make: an UpdateRate of 1 seems a bit excessive for the WebParsers in your skins.This is exactly what i was trying. An i think you are correct, only way to essentially stop the errors is to do a dummy value. Typically id say i wouldnt worry about it since its just upon start but i saw a few times while testing where that webparse like hung up and couldnt pull the info for a few mintue and log was flooded with the error until it was able to get a value.
I mean, sure, you'd generally want live sports skins to be close to a real-time updating and unless instructed otherwise via Flags the WebParser measures will cache requests and only download stuff if it has changed, but still, polling these URLs every second should be avoided. Not sure which is these sites' APIs limit of requests per day, but besides hanging WebParser, you or your suite's users could get blocked or banned for polling them too frequently. I'd go with a less intensive UpdateRate, say, 60 for a minute, or something like that. The resources you use are too comprehensive and well made to potentially be "lost" because of excessive usage. Just saying...
Statistics: Posted by Yincognito — Today, 5:02 am