Quote:
Originally Posted by ratdude747
(Speaking as one of the scorekeepers on Hopper)
This was due to internet connection speed issues between the scorpion (field computer case) and NASA (where our internet and backups come through), not an API problem. With sync enabled it would take too long for scores to be committed to the database and backed up (what happens between the head ref giving a thumbs up and the score being posted to the audience screen). It was slow without the syncing issue (supposedly due to FMS changes to allow for two Einstein fields)... but with sync enabled it was so bad that it would time out half the time.
Sorry about that... We at least (AFAIK) updated things over lunch break and after the last match of the day...
|
From what I gather, sending scores to FIRST's servers required a full database upload from FMS, which was slow due to the limited bandwidth. A match score should only be a few KB. The problem seems to be that FIRST hacked the API to use the data from the full database dump instead of implementing a lower overhead solution.