cartodb4/dataservices-api
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

added best practices as an H3 under the Overview, data services api integration section

Browse Source
This commit is contained in:
csobier
2016-04-26 12:31:08 -04:00
parent ee13920a8e
commit e70794a620
4 changed files with 15 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/quota_information.md
+4 -1
View File
@@ -7,5 +7,8 @@
Quota consumption is calculated based on the number of request made for each function. Be mindful of the following usage recommendations when using the Data Services API functions:
* One credit per function call will be consumed. The results are not cached. If the query is applied to a _N_ rows dataset, then _N_ credits are consumed
* Avoid running dynamic queries to these functions in your maps. This can result in credit consumption per map view. **Note:** Queries to the Data Services API, and any of its functions in your maps, may be forbidden in the future
* Avoid running dynamic queries to these functions in your maps. This can result in credit consumption per map view.
**Note:** Queries to the Data Services API, and any of its functions in your maps, may be forbidden in the future
* It is advised to store results of these queries into your datasets, and refresh them as needed. This ensure more control of quota credits for your account