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.
 

The King is dead, long live the new King! (API switched ownerships!)

First post
Author
Kossaw
Body Count Inc.
Mercenary Coalition
#121 - 2014-02-06 00:45:27 UTC
Skutter Midumulf wrote:
Katrinya wrote:
Where the bloody heck is CREST?

Why even bother this dead horse of an API?


This.


Remember the chaos when CCP finally killed the old API system and you had to move to new CAK's ? Can you even imagine having to re-write every single 3rd party application out there from API into CREST ( not to mention REST isn't at all necessary when the only thing you are doing is reading from the server )

WTB : An image in my signature

rswfire
#122 - 2014-02-06 04:26:11 UTC  |  Edited by: rswfire
CCP Prism X wrote:
WONTDO List:
Planetary Interaction API - Data schema simply incompatible with API.


Would you please reconsider your position on this one?

It doesn't have to be complex.

In our case, what would be helpful is knowing what planets a character has command centers, what commodities are being extracted or produced, and the time until those extractors are scheduled to end. Maybe beyond that just a list of assets (commodities) that can be transported to a Customs Office.

This would go a long way toward making it possible for us to create tools that help us keep track of PI installations. On a personal level, we can make sure we're re-installing our extractor programs when they finish. Currently, there is no way to automate this like you would with EveMon and your skill queue. On a group level, such as a corp or alliance, it would help us better manage projects where many people are "chipping in" different commodities toward a common end.

I don't understand what you are saying when you say "data schema incompatible with API." The API outputs XML. What data is not compatible with XML? I can understand that it might be more challenging to represent a complete PI installation in XML, but you are already doing this in your databases or PI wouldn't even exist. But putting that aside, most of us do not need anything that complicated.

With the advent of POCOs, this becomes an even more important aspect of Eve that is missing from the API. You guys have been great at providing us with important data we can use, but this is one area that has been neglected. I did some Googling and this has been asked for since as early as 2011, so it is needed/wanted.

Please reconsider your stance on this.

It doesn't have to be complicated -- some basic data is enough for 95% of the ways in which it would likely be used.
CCP FoxFour
C C P
C C P Alliance
#123 - 2014-02-07 20:09:33 UTC
rswfire wrote:
CCP Prism X wrote:
WONTDO List:
Planetary Interaction API - Data schema simply incompatible with API.


Would you please reconsider your position on this one?

It doesn't have to be complex.

In our case, what would be helpful is knowing what planets a character has command centers, what commodities are being extracted or produced, and the time until those extractors are scheduled to end. Maybe beyond that just a list of assets (commodities) that can be transported to a Customs Office.

This would go a long way toward making it possible for us to create tools that help us keep track of PI installations. On a personal level, we can make sure we're re-installing our extractor programs when they finish. Currently, there is no way to automate this like you would with EveMon and your skill queue. On a group level, such as a corp or alliance, it would help us better manage projects where many people are "chipping in" different commodities toward a common end.

I don't understand what you are saying when you say "data schema incompatible with API." The API outputs XML. What data is not compatible with XML? I can understand that it might be more challenging to represent a complete PI installation in XML, but you are already doing this in your databases or PI wouldn't even exist. But putting that aside, most of us do not need anything that complicated.

With the advent of POCOs, this becomes an even more important aspect of Eve that is missing from the API. You guys have been great at providing us with important data we can use, but this is one area that has been neglected. I did some Googling and this has been asked for since as early as 2011, so it is needed/wanted.

Please reconsider your stance on this.

It doesn't have to be complicated -- some basic data is enough for 95% of the ways in which it would likely be used.


I make ZERO promises, but I will at least talk to CCP PrisimX and see what might possibly be possible. I have no idea, but I will ask some questions.

@CCP_FoxFour // Technical Designer // Team Tech Co

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

Ideki
Wolf Brothers INC
United Neopian Federation
#124 - 2014-02-11 13:44:22 UTC
CCP FoxFour wrote:
rswfire wrote:
CCP Prism X wrote:
WONTDO List:
Planetary Interaction API - Data schema simply incompatible with API.


Would you please reconsider your position on this one?

It doesn't have to be complex.

In our case, what would be helpful is knowing what planets a character has command centers, what commodities are being extracted or produced, and the time until those extractors are scheduled to end. Maybe beyond that just a list of assets (commodities) that can be transported to a Customs Office.

This would go a long way toward making it possible for us to create tools that help us keep track of PI installations. On a personal level, we can make sure we're re-installing our extractor programs when they finish. Currently, there is no way to automate this like you would with EveMon and your skill queue. On a group level, such as a corp or alliance, it would help us better manage projects where many people are "chipping in" different commodities toward a common end.

I don't understand what you are saying when you say "data schema incompatible with API." The API outputs XML. What data is not compatible with XML? I can understand that it might be more challenging to represent a complete PI installation in XML, but you are already doing this in your databases or PI wouldn't even exist. But putting that aside, most of us do not need anything that complicated.

With the advent of POCOs, this becomes an even more important aspect of Eve that is missing from the API. You guys have been great at providing us with important data we can use, but this is one area that has been neglected. I did some Googling and this has been asked for since as early as 2011, so it is needed/wanted.

Please reconsider your stance on this.

It doesn't have to be complicated -- some basic data is enough for 95% of the ways in which it would likely be used.


I make ZERO promises, but I will at least talk to CCP PrisimX and see what might possibly be possible. I have no idea, but I will ask some questions.



Thank you.
Please we count on you for this.
Be our Champion. Big smile
Quesa
Macabre Votum
Northern Coalition.
#125 - 2014-02-13 18:33:44 UTC
PLEASE add corporation and alliance tickers to the new API. I, and some others, tend to use the ticker for displaying information over the entire name string and in order to get the info for both corporation and alliance you have to hit the api server 2 more times.

The current implementation of the AllianceList seems very inefficient. I don't know anyone that really needs a complete list of each Alliance in the game. It makes more sense to me to allow a developer to query information on a single alliance instead of downloading the entire XML sheet each time we want to update the data.
rswfire
#126 - 2014-02-14 03:00:09 UTC  |  Edited by: rswfire
CCP FoxFour wrote:
I make ZERO promises, but I will at least talk to CCP PrisimX and see what might possibly be possible. I have no idea, but I will ask some questions.


Thank you. I can see why the DUST community admires you so much.

I really appreciate your willingness to look into this. Something else crossed my mind after I read your post: there would also be value in being able to query the tax rates and owners of the POCOs for different planets. Perhaps a separate query for planetary information in a solar system? If I could query a system and get a list of planets, their types, and the POCO rates, there is a lot we can do with that.
Tahnil
Gunboat Commando
#127 - 2014-02-14 12:17:40 UTC
rswfire wrote:
CCP FoxFour wrote:
I make ZERO promises, but I will at least talk to CCP PrisimX and see what might possibly be possible. I have no idea, but I will ask some questions.


Thank you. I can see why the DUST community admires you so much.

I really appreciate your willingness to look into this. Something else crossed my mind after I read your post: there would also be value in being able to query the tax rates and owners of the POCOs for different planets. Perhaps a separate query for planetary information in a solar system? If I could query a system and get a list of planets, their types, and the POCO rates, there is a lot we can do with that.


I don‘t like the idea of querying the API for the owners of customs offices. Why? Just try to imagine how nullsec alliances would react to the proposal to allow API calls for who has got a POS on some moon. This would be free and very convenient intel for everybody who is interested in "acquiring" this spot.

I have no problem with other planetary data and tax rates being available via API though.
rswfire
#128 - 2014-02-14 13:26:44 UTC  |  Edited by: rswfire
Tahnil wrote:
I don‘t like the idea of querying the API for the owners of customs offices. Why? Just try to imagine how nullsec alliances would react to the proposal to allow API calls for who has got a POS on some moon. This would be free and very convenient intel for everybody who is interested in "acquiring" this spot.

I have no problem with other planetary data and tax rates being available via API though.


Querying the owner of a POCO is not the same thing as querying data on a moon with a POS. They are wholly separate things. POCOs are planet-wide structures; the moons are not even relevant in this context. If you put up a POCO, you're taking over aspects of a system that make you noticeably more public than a POS does. It's information I can learn with very little effort, but I think your argument is "no free intel" and it's a fair point that you could query every system in Eve. I don't see the problem there (putting up a POCO puts you in the spotlight; it seems like something that should qualify as public data), but the tax rates are most important. Much of this information is already available in the data dumps, from system and planet information to commodity listings. It's just very generic data. With the advent of greater user control where data is no longer static, we need a programmatic way of obtaining current information.