3 ms·
Could somebody explain this more simply? As I understand it, the site had no usage quota, it was the end user (ultimately the browser making the map API reques
by skeletonjelly 15y ago
Could somebody explain this more simply?
As I understand it, the site had no usage quota, it was the end user (ultimately the browser making the map API request). The end user had a limit but as this was in the hundreds or thousands (can't recall) it was not real concern for your average end user.
Is this what's changing? The site is now accountable for request quota?
- intev 15y agoMy understanding is that the site was always responsible for the usage quota. The calls made (even on the client side) technically is made by the website, so the limit applies to the website. If requests come from the end user and not the site (as you mention), very few people would hit that limit and it would not be a concern.
- jcampbell1 15y agoThat is correct. It used to be unlimited, with requests rate limited per IP/visitor to prevent abuse. It will now be 25,000 free loads per day per site, and $4 per 1000 loads after that.