Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rules for historic data #72

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/esi_introduction.md
Original file line number Diff line number Diff line change
@@ -83,10 +83,11 @@ Some endpoints, specifically for sending mail and reading contracts, have intern
The 520 error is counted in the error limit.

#### Spread Load

ESI is a shared resource and projects should be optimized to have minimum consumption of unnecessary resources. In the case of long running
services, consistent amounts of slow traffic are preferred to spiky, high throughput traffic.

#### Historic Data
You can get banned for high load on endpoints with historic data (killmails/wars/others?). There are no specifications about what constitute high load, that is entirely up to CCP to decide as needed. Killmails are usually safe with less than 50 rps (requests per second). Wars are usually safe with less than 20 rps. But, there are no guarantees - this isn't a official CCP policy! It's simply advice from another 3rd party developer.

#### User Agent
When making requests, it's recommended you set a `User-Agent` header in your client which includes the source of the request and contact information. This way, CCP can identify and help you with issues if you're banned.