Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 1 post(s) |
Necrothitude
Caldari Socialites Of The Crazy Horse Saloon The Economy
|
Posted - 2008.12.23 10:46:00 -
[1]
Just a few things I'd like for the API to provide for:
- Item Database. Please, CCP, don't make me write code which walks all over your poor wiki! Please! I beg you!
- Market value indexes for ore and minerals, by region. Not that hard, even if they were cached for 12 hours or more it'd be so much better than nothing at all! hint: attach this information to the item database, then you'd have information for everything!
- Please add some more information about characters! Specialization and ancestry, specifically.
Suggestion for the Item Database: assign each item type a unique integer id (they probably already have one for internal database purposes, I would suspect). Allow a vague list to be retrieved of all items (eg: <xml eveapi_version="0"> <item id="0">Exotic Dancers</item> <item id="1">Janitors</item> ... </xml>
and so on and so forth. provide another API url, with one of the POST arguments being the item ID. Overall I think my suggestion is largely homologous with the existing API structure, but it could possibly be organized better.
What do you think, fellow API slaves? Registered Linux Addict #431495 http://profile.xfire.com/mrstalinman | John 3:16! http://www.fsdev.net/ | http://lordsauron.wordpress.com/ |
Lumy
Minmatar eXceed Inc. Atlas Alliance
|
Posted - 2008.12.23 11:43:00 -
[2]
Item Database: I don't think this is necessary/good idea. You are talking about more than 15000 inventory types, that would translate to several MB large XML. Just use DB dump as the rest of us. Follow the linkie.
Market value: IIRC Eve Central provides service like that. Check it out. But I agree official version would be cool.
More character info: DEFINITELY!
Joomla! in EVE - IGB compatible CMS. |
|
CCP Lingorm
C C P
|
Posted - 2008.12.23 11:43:00 -
[3]
The item database information you are after is supplied in the Static Database export we provide.
It will not be provided in the API.
It is also interesting to note that the Item DB in the wiki is built using the Static Data DB Export.
CCP Lingorm CCP Quality Assurance QA Engineering Team Leader
Originally by: Lord Fitz Eve is to WoW as Wow is to an 8 player game of Unreal Tournament.
|
|
Hagen Stein
Biotronics Inc. Alternative Realities
|
Posted - 2008.12.23 14:25:00 -
[4]
Edited by: Hagen Stein on 23/12/2008 14:28:36 Necro,
you might find this thread interesting: http://oldforums.eveonline.com/?a=topic&threadID=930094
|
Vorononv Circut
Opinicus Operations Vanguard.
|
Posted - 2008.12.24 02:52:00 -
[5]
Originally by: CCP Lingorm The item database information you are after is supplied in the Static Database export we provide.
It will not be provided in the API.
It is also interesting to note that the Item DB in the wiki is built using the Static Data DB Export.
He's right... Evelopedia Linkage. So now the official item db does not say what drone poo refines into. Suggestion: Please Please put it in the database export.
|
Mister Stalin
|
Posted - 2008.12.29 08:44:00 -
[6]
Originally by: Lumy Item Database: I don't think this is necessary/good idea. You are talking about more than 15000 inventory types, that would translate to several MB large XML. Just use DB dump as the rest of us. Follow the linkie.
Market value: IIRC Eve Central provides service like that. Check it out. But I agree official version would be cool.
More character info: DEFINITELY!
Both extremely good resources, thank-you!
It still leaves me wanting for an API Item DB, 'cause I already have a legion of XML parsing going on for everything else. If you use Java, the org.w3c.dom parser is massively excellent! It's the W3C reference XML parser, so it's wicked fast!
The Official listings for manufacturing materials is kinda a must... I'm seriously surprised that it's not already there in the API. Just provide an enumeration for all the various regions in EVE, then add that region to the POST request for the 24-hour cached price index XML. Not complex, and I can't imagine it taking a lot of load to implement - well, server load. I suppose allocating a programmer to work on it has other kinds of opportunity costs that make it impossible to respond to my every fickle whim.
|
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |