These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE Technology Lab

 
  • Topic is locked indefinitely.
 

CREST API Help Needed

First post First post
Author
Previous Topic Next Topic
Brian Paignton
Investment Grade Metals
#1 - 2014-10-15 11:41:47 UTC
Hi,

I'm having some trouble with the CREST API and hope that someone can help me.

I've been reading the CREST documentation (located at https://developers.testeveonline.com/resource/crest).

Quote:
All resources are reachable from the root API entry point URI. Clients should not construct URIs, but instead follow URIs included in representations they have received.


With that in mind my first call to the API is as follows...

http://public-crest.eveonline.com

... which gives me back a links to a number of resources that I can use.

First problem
If I follow http://public-crest.eveonline.com/industry/teams/ and from the returned RESTful document I then follow http://public-crest.eveonline.com/solarsystems/30000159/ I get an error message as follows:

Quote:
{
"message": "The route was not found",
"key": "routeMissing",
"exceptionType": "NotFoundError"
}


This looks like a routing issue (possibly WebAPI) - is this an error on my part or have CCP not implemented that URI yet?

Second Problem
When I made a request for teams (in above example) the data took a really long time to come back. I would estimate around 5 minutes. Is this because the system isn't fully up and running yet? I wanted to do some industrial calculations using the list of systems and their current industrial indexes but that data takes so long to come back.

Would appreciate any feedback on my problems and corrections to what I am doing if I am doing something wrong.

Thanks,
Brian
CCP FoxFour
C C P
C C P Alliance
#2 - 2014-10-15 12:28:24 UTC
public CREST != CREST

Not everything is exposed via public CREST

CREST is still not out.

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
Brian Paignton
Investment Grade Metals
#3 - 2014-10-15 13:44:01 UTC
Thanks for the clarification.

Regarding my second point - the service is performing fine. The client I was using was transforming the returned response into "beautified" JSON which was taking a long time and giving the impression that the service was slow.
CCP FoxFour
C C P
C C P Alliance
#4 - 2014-10-15 14:00:43 UTC
Brian Paignton wrote:
Thanks for the clarification.

Regarding my second point - the service is performing fine. The client I was using was transforming the returned response into "beautified" JSON which was taking a long time and giving the impression that the service was slow.


Probably took time to beautify the JSON. This data is meant to be ingested by code, not viewed directly. A few tests showed a maximum response time of 253ms for me though.

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
Steve Ronuken
Fuzzwork Enterprises
Vote Steve Ronuken for CSM
#5 - 2014-10-16 15:27:50 UTC
If you need data which doesn't change (like the names of star systems), the SDE is the place to get it. (there are converted versions on my site, if MS SQL doesn't appeal)

Woo! CSM XI!

Fuzzwork Enterprises

Twitter: @fuzzysteve on Twitter
Taupwnz
Native Freshfood
Minmatar Republic
#6 - 2014-10-19 19:43:55 UTC
Wonder if you could add paging to the CREST right away. For me its about 3208 ms loading time for GET /industry/teams/

And is there some doc. about what is public CREST endpoints and what's CREST to have clear understanding what's going on ?

sorry for bad English.
CCP Nullarbor
C C P
C C P Alliance
#7 - 2014-10-19 22:05:06 UTC
Taupwnz wrote:
Wonder if you could add paging to the CREST right away. For me its about 3208 ms loading time for GET /industry/teams/

And is there some doc. about what is public CREST endpoints and what's CREST to have clear understanding what's going on ?

sorry for bad English.


Pagination won't actually help if it's the kind of resource where you need all the data anyway. Filtering to only fetch based on region or solarsystem might, but in reality this particular resource is not really big enough to warrant doing that either.

Response times will vary depending on whether we have already warmed our cache for this request. If bandwidth is a problem for you, try enabling gzip compression on your request which will bring the response size down to about 230k.

CCP Nullarbor // Senior Engineer // Team Game of Drones
Max Kolonko
Caldari Provisions
Caldari State
#8 - 2014-10-20 06:04:55 UTC
CCP Nullarbor wrote:
Taupwnz wrote:
Wonder if you could add paging to the CREST right away. For me its about 3208 ms loading time for GET /industry/teams/

And is there some doc. about what is public CREST endpoints and what's CREST to have clear understanding what's going on ?

sorry for bad English.


Pagination won't actually help if it's the kind of resource where you need all the data anyway. Filtering to only fetch based on region or solarsystem might, but in reality this particular resource is not really big enough to warrant doing that either.

Response times will vary depending on whether we have already warmed our cache for this request. If bandwidth is a problem for you, try enabling gzip compression on your request which will bring the response size down to about 230k.


Have You tried putting cache servers in some warmer environment for better performance? Maybe next to an oven? Or just turning off AC in server room? :P

Read and support: Don't mess with OUR WH's What is Your stance on WH stuff?