civicpy-specific endpoints on CIViC production
ahwagner opened this issue · 2 comments
ahwagner commented
Currently, we do some very large (and low-count) requests. This might not be captured by CIViC's throttling mechanism, which is request count based. We may want to consider the strategies to mitigate widespread adoption of CIViCpy, particularly if we fail to update our nightly civicpy cache and clients revert to hard (API-driven) updates.
@susannasiebert and @acoffman what do you think?
ahwagner commented
@acoffman has suggested elsewhere that we consider civicpy-specific endpoints. Renaming issue to reflect this proposal.
susannasiebert commented
This has been superseded by #108