There isn’t a lot of javascript in the TD/A interface, just enough to give us the ability to validate logins.
We have an occasional problem with a click on the submit button causing multiple submits that I may have to use Javascript to get around, because it can result in double charges to someone’s credit card. This is a know problem with the mouse interface, though shakey hands can also cause it. There are sequencing tricks that can be used on the server end to help detect double submits, but they’re not 100% effective.
The plan for the custom supplement update feature is that you give us a starting date and I give you every record that has had a ratings or membership status change since then. Once you download a ‘gold master’ file, you should be able to keep it up to date with relatively small updates.
With about 72,000 membership transactions a year, in a typical month there would be somewhere around 6000 records to download because of membership issues plus however many members have had a ratings change in that time frame. And if you are downloading only official published ratings as opposed to the latest rating, then the only time you would need to download the roughly 12,000 members in a typical supplement is every other month.
So, if you updated every other month you’d generally be downloading around 24,000 records, which is a lot better than downloading 600,000 records.
I suspect many active TDs will want to update more frequently than bi-monthly, probably syncing their computer with the USCF’s before they direct their next event.
We could offer ‘regional’ updates, of say only the players in CA and surrounding states, but I’m not sure that saves enough downloading time to be worth the effort.
We’re already starting to see some indication that the TD/A activity will be related to tournament directing cycles. I see numerous small batches of new and returning members on Friday, probably corresponding to advance registration, and bigger ones on Saturday evening and on Sunday, with rating reports more likely to be posted on Monday or Tuesday. (That’s significant mostly because I need to know when I can schedule some maintenance tasks.)
There’s no reason why the pairing programs couldn’t be set to automatically log in and initiate a download of whatever it needs to update itself, but that’s something that would have to be worked out between those authors and us.