|
as a suggestion you'd be better having something cache that information from the DNAS instead of it hitting the DNAS all the time from a website (though I'm hoping to add some caching on the stats responses to the next v2.2.x release) as querying them at such a low polling level isn't going to give much variation in what gets returned i.e. how many listeners are going to connect in say a second which are otherwise going to be noted in a second later response update.
though it also depends on what it was trying to hit as v2.0 doesn't have the /7.html response and will incorrectly treat it like a source connection in some cases which again is something v2.2 helps resolve along with more appropriate handling of inconclusive connection attempts.
|