I just updated the system to version 1.3p. The previous discussion about scrape times made me realize (about five minutes ago) that the scrape time limit was per user, so if ten people were viewing the page, then it would scrape ten times as fast, even though each individual user would still see it only as often as the scrape time permitted - an obvious flaw. But it's fixed now, and the system will not scrape data from FIRST if it hasn't been long enough.
I kind of hurried this out, so it hasn't had the proper bug testing. It was a simple change and shouldn't have caused any, but if anything stops working, please tell me.
Another minor change: the "last updated on" notice is now at the bottom, not the top.
There have been fifteen downloads at the time of this posting.
Quote:
Originally Posted by Andrew Schreiber
You other option, and one I just never got around to implementing, would be to check the Last-Modified header and see if it has changed since your cached version.
|
Unfortunately, that still means that the connecting has to occur, because the header isn't sent from FIRST unless an http request is sent. The only benefit of using that header, that I can think of, would be to reduce load on the server implementing the API, because then it wouldn't have to process the data. If you look at the function library, it uses a seriously ginormous number of string operations and array manipulations. Am I totally wrong about the usage of that header?