I've been following the "progress" of the spreadsheets API for over year, and I think you'll be a happier, healthier human being if you find a good alternative before it is too late.
Just a couple of weeks ago, they closed a whole lot of significant long-term bugs with the comment "this issue will be fixed in an upcoming version of the API" (well, mostly - some said "MAY be fixed"). Not, "we fixed it, have fun guys" but "we are intending to fix it, get off our back morons". Many of these bugs were over 9 months old. Unless Google can trouble themselves to share their wonderful plans for the future along with some time-lines, I'd run while you can. The sad fact is that nobody cares that your SS took 60 seconds to download. cheers, David. On Sat, Dec 10, 2011 at 1:08 PM, adam sah <[email protected]> wrote: > oops, forgot to mention-- I tested this both on app engine and locally > from several network locations-- > the latency is definitely server-side. > > adam > > > On Fri, Dec 9, 2011 at 6:03 PM, adam sah <[email protected]> wrote: > >> example request: >> >> INFO 2011-12-10 01:59:59,379 remote_spreadsheet.py:179] force=True >> fetching https://spreadsheets.google.com/feeds/list/0AqtkK-...(keyhidden for >> security reasons).../3/public/values?rnd=1323482399 >> INFO 2011-12-10 02:00:56,986 remote_spreadsheet.py:232] saving: >> key=0AqtkK-... >> >> i.e. 60 seconds to download a SS. >> >> this is originating from an app engine app that reads from thousands of >> SSs-- while we cache the heck out of them, we do need to reload from time >> to time. >> >> thanks, >> adam >> >> >
