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 Information Portal

 
  • Topic is locked indefinitely.
 

Dev blog: Upcoming API Changes for Industry

First post First post
Author
Previous Topic Next Topic
CCP FoxFour
C C P
C C P Alliance
#21 - 2014-06-18 15:54:24 UTC
Dread Nanana wrote:
The new API is a little less useful for invention outcomes.

Inventions really require completion status.. Fail/Success is quite important for them and having that information cached for 24h is somewhat less useful. Perhaps current jobs should return active jobs + completed jobs in the last 24h. That would avoid need to fetch history very often or at all.

The 1000 limit for history is of course better than the current one of 150 or so, which our industrial corp could overflow in a matter of hours.

If the API stays as is, is the history jobs endpoint cached globally or can 6 director keys result in effective 4h cache if queried in turn? (every 4h)


Also I will ask about the success/failure thing. :)

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
Skutter Midumulf
Proioxis Assault Force
Rogue Caldari Union
#22 - 2014-06-18 16:13:02 UTC
CREST should make transitions like this much easier as it's support for explicit representations (http://web.archive.org/web/20130103002534/http://wiki.eveonline.com/en/wiki/CREST_Documentation#Representations) means that old and new APIs can co-exist while apps migrate and then requests for old representations can return errors after the migration period without requiring new endpoints or confusing old apps with new data formats.

It's great to see the REST in CREST being useful!
Bertrand Prout
Sunday Sessions
#23 - 2014-06-18 16:25:04 UTC
With these changes, will it be possible to retrieve Reverse Engineering jobs from with the API?
Querns
Science and Trade Institute
Caldari State
#24 - 2014-06-18 16:37:02 UTC
A small bug report with the team specialties CREST endpoint: It looks like specialty ID #40 is missing its label.

http://i.imgur.com/mFMkzoS.png

This post was crafted by the wormhole expert of the Goonswarm Economic Warfare Cabal, the foremost authority on Eve: Online economics and gameplay.
CCP FoxFour
C C P
C C P Alliance
#25 - 2014-06-18 16:41:59 UTC
Querns wrote:
A small bug report with the team specialties CREST endpoint: It looks like specialty ID #40 is missing its label.

http://i.imgur.com/mFMkzoS.png


Known issue. :) Thank you though! :D

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
Imperator Universitas
Stimulus
Rote Kapelle
#26 - 2014-06-18 16:42:00 UTC  |  Edited by: Imperator Universitas
Heya folks, I was reading this over. I know everything is changing, but I think it'd be a pretty good idea to embed a new tag in the current XML for the replacement of the current call. You could also embed a text message with the sunset date of the current call.

That way when you are debuging your tools {if you are doing it properly} you will see both; that the XML feed you pulled contains helpful info on what you should be looking up, and what time you have to do it by.

If your parser behaves like it's supposed to, an extra tag will be ignored by execution code, but using your debugger or a full display you'll see it. If it breaks someone's tool, I'll be honest, that code was garbage.

Just a thought...
--Imp
CCP FoxFour
C C P
C C P Alliance
#27 - 2014-06-18 16:43:13 UTC
Skutter Midumulf wrote:
CREST should make transitions like this much easier as it's support for explicit representations (http://web.archive.org/web/20130103002534/http://wiki.eveonline.com/en/wiki/CREST_Documentation#Representations) means that old and new APIs can co-exist while apps migrate and then requests for old representations can return errors after the migration period without requiring new endpoints or confusing old apps with new data formats.

It's great to see the REST in CREST being useful!


Yes! We are using that in several places, most notably the tournaments realtime resource has two versions. The whole time we were talking about what we should do for the API we were thinking "god this would be easier in CREST" >.<

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
Meytal
Doomheim
#28 - 2014-06-18 16:43:57 UTC
By any chance is it possible to adjust the 24 hour timers to be slightly less, say 23 or 23.5 hours? Then we can have timers set for 24 hours and it won't depend on client/network/server latency for us to get a real 24 hour report, since that's a really nice, round number.
CCP FoxFour
C C P
C C P Alliance
#29 - 2014-06-18 16:51:34 UTC
Meytal wrote:
By any chance is it possible to adjust the 24 hour timers to be slightly less, say 23 or 23.5 hours? Then we can have timers set for 24 hours and it won't depend on client/network/server latency for us to get a real 24 hour report, since that's a really nice, round number.


When we set the timers for "24 hours" we tend to set them to 23.5 cause of that reason, we still say 24 though or people would be like "you said 23.5 so can you make it 23" and it's just a losing battle.

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
CCP FoxFour
C C P
C C P Alliance
#30 - 2014-06-18 17:00:55 UTC  |  Edited by: CCP FoxFour
OK so I straight up lied... well lie would mean I did it on purpose but the fact is I was completely wrong.

The jobs endpoint is cached for 15 minutes and the history one for 6 hours. Thats vs the 1 hour and 24 hours that I had said in the dev blog. /derp

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
Ydnari
Estrale Frontiers
#31 - 2014-06-18 18:06:09 UTC
Is this going to lead to awkward situations where short jobs that were both started and completed since the last query of the running jobs endpoint are going to be invisible for up to 6 hours until the historical jobs API can be queried again?

Nice that the running one has a short cache timer on it though.

I wonder, could the running one actually show both running now, and started in the last 6 hours, so that it covers any gaps with the historical one?

--
Scarna Jenari
Tritanium Industries and Technology
Goonswarm Federation
#32 - 2014-06-18 18:14:43 UTC
No API for owned blueprint details?
Meytal
Doomheim
#33 - 2014-06-18 18:15:30 UTC
CCP FoxFour wrote:
When we set the timers for "24 hours" we tend to set them to 23.5 cause of that reason, we still say 24 though or people would be like "you said 23.5 so can you make it 23" and it's just a losing battle.

\o/

Thanks!
CCP FoxFour
C C P
C C P Alliance
#34 - 2014-06-18 18:27:45 UTC
Scarna Jenari wrote:
No API for owned blueprint details?


Soon(tm)

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.
Joshua Foiritain
Coreli Corporation
Pandemic Legion
#35 - 2014-06-18 18:46:17 UTC
CCP FoxFour wrote:
Scarna Jenari wrote:
No API for owned blueprint details?


Soon(tm)


Joshua Foiritain wrote:
Any chance well ever see our API access log available through the API? Manually going over IP's is effort, i want to outsource it to our website.


Pretty please? Big smile

The Coreli Corporation is recruiting.
Sigras
Conglomo
#36 - 2014-06-18 19:52:11 UTC
as a side note, is the CREST API going to give the cost of different types of jobs for different systems?
Vaju Enki
Secular Wisdom
#37 - 2014-06-18 20:23:03 UTC
Api's FTW

The Tears Must Flow
probag Bear
Xiong Offices
#38 - 2014-06-18 23:11:18 UTC
CCP FoxFour wrote:
OK so I straight up lied... well lie would mean I did it on purpose but the fact is I was completely wrong.

The jobs endpoint is cached for 15 minutes and the history one for 6 hours. Thats vs the 1 hour and 24 hours that I had said in the dev blog. /derp


Whew. Came here to ask about that. The longer cache times could've really interfered with a laziness-enabling part of my tools. God forbid me having to actually remember what jobs I'd just inputted 15 minutes ago. Would've had to reshuffle my morning ritual of news + invention before coffee is ready.
Histracko
Intrasolar Dynamics
#39 - 2014-06-19 01:23:39 UTC
Any chance of a PI interface in the near future? Would be really useful for knowing when to be on to reset a production chain.
CCP FoxFour
C C P
C C P Alliance
#40 - 2014-06-19 01:32:56 UTC
Histracko wrote:
Any chance of a PI interface in the near future? Would be really useful for knowing when to be on to reset a production chain.


Like the one that was deployed on 2014/04/29: https://forums.eveonline.com/default.aspx?g=posts&m=4384137#post4384137

It has a few defects that I need to fix at somepoint but SO MUCH TO DO! ARG! :(

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.