| Author |
Thread Statistics | Show CCP posts - 184 post(s) |
brammator
SUB ZERO.
Legion of xXDEATHXx
97
   |
Posted - 2014.05.03 19:12:00 -
[1] - Quote
Idea: add Hardwirings info to char/CharacterSheet/AttributeEnhancers list
Idea: reveal Jump Clones (position, implants, hardwirings) info
Description: Could be separate endpoint, because char/CharacterSheet is HUGE already. Also Jump Clone timer, please.
Idea: split char/CharacterSheet into smaller endpoints
Description: or just add endpoints CharacterSkills, CharacterCertificates, CharacterRoles and CharacterBriefSheet. Last one would be CharacterSheet minus three previously named portions.
|
brammator
SUB ZERO.
Legion of xXDEATHXx
97
|
Posted - 2014.06.19 10:47:00 -
[2] - Quote
Idea: add CREST endpoint listing all available endpoints
Description: I'm sure you are using docstrings describing endpoint functions, but compiling them into useful document and laying it out could be boring and often forgotten chore. So why don't export it automagically? |
brammator
SUB ZERO.
Legion of xXDEATHXx
97
|
Posted - 2014.06.25 10:38:00 -
[3] - Quote
Idea: Rate-Limit headers
Description: I just saw wonderful feature in DigitalOcean API documentation:
RateLimit-Limit: 1200
RateLimit-Remaining: 1193
RateLimit-Reset: 1402425459
would be helpful to have same thing in CREST and API responses. Maybe not as HTTP headers but XML results in meta section.
|
brammator
SUB ZERO.
Legion of xXDEATHXx
98
|
Posted - 2014.07.21 14:49:00 -
[4] - Quote
I'm getting "RouteNotFound" for almost every CREST endpoint listed on http://public-crest-sisi.testeveonline.com/
Is that right? |
brammator
SUB ZERO.
Legion of xXDEATHXx
98
|
Posted - 2014.08.20 18:59:00 -
[5] - Quote
Idea: add labels to standings endpoint (both char and corp)
Because it would be very useful for coalitions/sides marking |
brammator
SUB ZERO.
Legion of xXDEATHXx
98
|
Posted - 2015.01.17 10:46:47 -
[6] - Quote
Could you add list of base urls to https://developers.testeveonline.com/resource/crest ? Also, https://developers.testeveonline.com/resource/crest/public-crest need some explanation.
EDIT.
I mean, it would be very helpful to know:
Are those limits applied for ip or for application? For example, I may have different apps at one host, so should I worry about total amount of requests?
What is "burst"?
Is there any signs that I am near limit? Maybe you could add some header with numbers to crunch. |
brammator
SUB ZERO.
Legion of xXDEATHXx
98
|
Posted - 2015.01.18 12:58:43 -
[7] - Quote
I'm using eveapi ( https://github.com/ntt/eveapi ) python library for XML api along with my own caching linrary ( https://github.com/brammator/glomp )
Storing api call results with (host, path, params) key goes well with XML eve api: it separates TQ from SiSi by host, inherently does security (via keyID=, vCode= in api call params) etc.
It doesn't go well with CREST: security code ("bearer" token) TTL is too short and passed differently (via HTTP header, not api call parameter), enpoints are duplicated on different hosts ("public" and "authed").
I could rewrite CREST API library to add refresh_token or app secret code to "params" list, but is it good solution? And what about data host deduplication? |
brammator
SUB ZERO.
Legion of xXDEATHXx
98
|
Posted - 2015.01.18 14:32:11 -
[8] - Quote
There is some good libs in development, I even abandon mine in favor of one of them ;-) Data is data, anyway, and api libs look pretty familiar, XML and CREST. |
| |
|