[Andrew Schreiber]

Looking at actual match data though, Michigan events were running on a 6-8 minute cycle time last year, some quick glances at other events shows this is pretty much normal. For now I will set the cache to expire every minute, this should mean we get match results quickly and without hammering too hard on anyone's machines. If I am consistently near my limits I will adjust the cache accordingly but it will NOT go to more than 50% of the average cycle time. (for last year this would be roughly 4 minutes) Would this be an acceptable solution?

Also, this is a heads up, the XML will change slightly, spaces in the tags shouldn't be there, I was really tired when I wrote that. I will also be putting an enclosing <Event> tag around everything. (if anyone has suggestions on what the XML should look like please tell me now)