speed of refreshing geocaches via geocaching4locus

[mambofive]

When refreshing a larger number (some more than 1000 caches) via gc4l, I get the attached message ("Slower! You've reached the limit of maximum actions / calls per minute").



I don't know the limitations of the gc API, but if there are limits for total number of refreshes and/or refreshes/minute, IMHO Locus should respect them and warn me (or reduce speed of refreshing) before getting stopped by gc.com.

This is not a big issue of course - I can split my caches and refresh them in several steps (and probably I should do some housekeeping on my device and clean up some old data...  )

[Menion]

hehe, this is problem in Geoaching4Locus, not in Locus. But Locus suffer from this also sometimes, mainly in GC Offlinizer. I'll post this to Arcao (G4L developer) topic, thanks

[Martin Sloup]

Damn! I didn't expected that someone reach the limit of calling 30 requests per minute (one request will update 10 caches), because Geocaching Live API server is known for slowness. But as I tested, it's not problem now to reach the limit when you update more than 300 caches. I will try to fix it in a next release.

[Martin Sloup]

Could you try this version:

https://www.dropbox.com/s/0frs6ahxxcpe2vq/Geocaching4Locus-1.5.4-rc4.apk

When I tried to update 571 caches with this version, it did not get an error any more.

[mambofive]

Seems like Seattle has added some more hamsters to their API servers ... ;-)
Your fix works perfectly, thank you!

Gesendet von unterwegs mit Tapatalk 2.