I've not been able to get through to MyCyclingLogs for a couple of days. Currently I'm getting Error 524 from CloudFlare, which appears to mean that the web server is taking too long to respond, which isn't good.
I think my Ticker will just use the last cached value it has, if it can't get a response from the website. I need to consider writing an equivalent of the MyCyclingLogs website, which could be far more tightly integrated with the Ticker, but as usual RealLife [TM] has been getting in the way. Shaun did give me a password to access the MySQL server, so we can certainly store the information on that, and conveniently, I've been hacking away using MySQL on one of our servers at work recently, so have become more familiar with it.
I'll have to dig out the details, and see if I can get a little proof-of-concept Mickey-Mouse version working. It would actually make the Ticker code far easier, since I wouldn't have to scrape the website and run RegEx's against it, as I have to do with MyCyclingLog, since that has a very poor API, which is totally unsuitable for our purposes. With a Ticker and MyCyclingLogs equivalent on the same website, they can both talk directly to the MySQL server, and doing things like pulling the last years worth of numbers (or last week, or last month ...) becomes relatively trivial, just a suitably crafted SELECT statement.
though a couple of people have said that the original ticker isn't updating unless I misunderstood the posts?
