Pages: [1] 2 3 :: one page |
|
Author |
Thread Statistics | Show CCP posts - 11 post(s) |
|
CCP Stillman
|
Posted - 2011.01.21 15:01:00 -
[1]
Hi everyone,
Here's a heads-up on the patch notes for Incursion 1.1.2. Exact schedule for when that will go out is to be announced, but following changes will be made when it goes live:
Wallet Journal changes:
- Lowered the cache timer for Wallet Journal calls to 27 minutes.
- Added legacy support for beforeRefID.
- Added maximum date range. You can now only query historical data a month back.
General changes:
- Fixed an issue with the API not returning name information on deleted corporationIDs and characterIDs
- Fixed a consistency issue with corporation member security. Element member renamed to row(Rowset style, as the rest of the API)
These are of course subject to change and all that if we find any critical bugs. This is just a warning about what we expect to be changing.
So please ensure that your applications will work come Incursion 1.1.2. We will be updating apitest.eveonline.com with these changes hopefully today, so that you can ensure compatibility.
|
|
Catari Taga
Centre Of Attention Middle of Nowhere
|
Posted - 2011.01.21 15:22:00 -
[2]
Originally by: CCP Stillman [list]Fixed an issue with the API not returning name information on deleted corporationIDs and characterIDs
Nice, the story used to be "by design" on that one, glad it finally gets fixed. --
|
|
CCP Prism X
Gallente C C P C C P Alliance
|
Posted - 2011.01.21 15:27:00 -
[3]
Originally by: Catari Taga
Originally by: CCP Stillman [list]Fixed an issue with the API not returning name information on deleted corporationIDs and characterIDs
Nice, the story used to be "by design" on that one, glad it finally gets fixed.
Oh that was by design.. guess I'll have to revert that then! *trollface*
~ CCP Prism X EVE Database Developer and Acting API Dude |
|
Catari Taga
Centre Of Attention Middle of Nowhere
|
Posted - 2011.01.21 15:31:00 -
[4]
Originally by: CCP Prism X *trollface*
indeed --
|
Hel O'Ween
Men On A Mission
|
Posted - 2011.01.21 16:15:00 -
[5]
Thx for the heads up, guys. Reduces those "WTF?!?" moments to a bearable amount. -- EVEWalletAware - an offline wallet manager |
Somerset Mahm
Somer's Omnibus Exploration and Reclamation Cognitive Distortion
|
Posted - 2011.01.22 06:35:00 -
[6]
Thanks to Stillman and Prism X for both putting up with my whining on IRC and for trying their best to compromise :) --- SOMER Lotteries SOMER Blink - new! SOMER Escrow Services |
Captain Thunk
Sniggerdly
|
Posted - 2011.01.22 13:38:00 -
[7]
Originally by: CCP Stillman
Added legacy support for beforeRefID.
Guessing this includes beforeTransID as well, if not I'm just reminding you
|
Line Stampen
|
Posted - 2011.01.22 14:12:00 -
[8]
Fix the bloody oveview, the rest is just meh
|
Marcel Devereux
Aideron Robotics
|
Posted - 2011.01.22 17:28:00 -
[9]
So we will have the ability to request one months worth of data at a time rather than walking the journal?
|
Catari Taga
Centre Of Attention Middle of Nowhere
|
Posted - 2011.01.22 18:08:00 -
[10]
Edited by: Catari Taga on 22/01/2011 18:09:13
Originally by: Marcel Devereux So we will have the ability to request one months worth of data at a time rather than walking the journal?
No, after the change you will be limited to walk the journal back one month only is what I understood (currently you can go several months back). --
|
|
Dragonaire
Caldari Corax. SOUL CARTEL
|
Posted - 2011.01.23 06:55:00 -
[11]
Another little bug I've notice is with the skills rowset in CharacterSheet. The columns attribute still shows unpublished but there is no unpublished attribute in rows. My bug report on it is 106374.
<rowset name="skills" key="typeID" columns="typeID,skillpoints,level,unpublished"> should be <rowset name="skills" key="typeID" columns="typeID,skillpoints,level">
Also could a new category be added to bug reporting just for API as I'm never sure which to use for them. |
Desmont McCallock
|
Posted - 2011.01.23 09:30:00 -
[12]
Originally by: Dragonaire Another little bug I've notice is with the skills rowset in CharacterSheet. The columns attribute still shows unpublished but there is no unpublished attribute in rows. My bug report on it is 106374.
<rowset name="skills" key="typeID" columns="typeID,skillpoints,level,unpublished"> should be <rowset name="skills" key="typeID" columns="typeID,skillpoints,level">
Also could a new category be added to bug reporting just for API as I'm never sure which to use for them.
I'm under the impression that the "unpublished" attribute shows up only when a character sheet contains a non-public skill, taking the value of 1. Could be wrong though. |
|
CCP Stillman
|
Posted - 2011.01.23 16:51:00 -
[13]
Originally by: Desmont McCallock
Originally by: Dragonaire Another little bug I've notice is with the skills rowset in CharacterSheet. The columns attribute still shows unpublished but there is no unpublished attribute in rows. My bug report on it is 106374.
<rowset name="skills" key="typeID" columns="typeID,skillpoints,level,unpublished"> should be <rowset name="skills" key="typeID" columns="typeID,skillpoints,level">
Also could a new category be added to bug reporting just for API as I'm never sure which to use for them.
I'm under the impression that the "unpublished" attribute shows up only when a character sheet contains a non-public skill, taking the value of 1. Could be wrong though.
You're correct. But it turns out that when we added all unpublished skills to the skiltree, we introduced a bug where the unpublished flag on the charactersheet disappeared. So we'll fix that |
|
|
CCP Stillman
|
Posted - 2011.01.23 17:11:00 -
[14]
Originally by: Catari Taga Edited by: Catari Taga on 22/01/2011 18:09:13
Originally by: Marcel Devereux So we will have the ability to request one months worth of data at a time rather than walking the journal?
No, after the change you will be limited to walk the journal back one month only is what I understood (currently you can go several months back).
You'll be able to walk one month back, in increment of 256 entries as the rowCount.
|
|
Selene D'Celeste
Caldari The D'Celeste Trading Company ISK Six
|
Posted - 2011.01.23 21:06:00 -
[15]
Was the ability to multi-pull corp wallets actually adversely affecting the servers? There are not a lot of people who can use this to their advantage ... but the impact affects literally thousands of EVE players since the gaming establishments that benefit from quick deposit turnaround are used by many, many people.
Given how many hundreds of thousands of characters and corporations constantly poll the API, I would be surprised if this was due to performance. ______________________________
|
Marcel Devereux
Aideron Robotics
|
Posted - 2011.01.24 19:26:00 -
[16]
Walking this data isn't really efficient for mobile devices. Can we just return all available data from a given transactionID or refID with up to a months worth of data? For anything but the initial sync it would require less requests to the server and subsequent requests will be smaller by specifying the last seen transactionID or refID.
|
|
CCP Stillman
|
Posted - 2011.01.24 22:01:00 -
[17]
Added:
- Will no longer error on illegal CharacterName input but rather remove bad input from the list of resolved IDs.
- Scotty the Docking Manager will no longer refuse to service character sheets.
|
|
Neutrino Sunset
Bene Gesserit ChapterHouse Sanctuary Pact
|
Posted - 2011.01.26 09:52:00 -
[18]
Since the roll out of Incursion the behaviour of the API for walking the wallet journal has obviously changed, it used to return 1000 entries per call and now returns 50, breaking all code which uses it.
The documentation on this website here http://www.eveonline.com/api/doc/data-account.asp is now completely incorrect, as is the documentation here on Eve Dev http://wiki.eve-id.net/APIv2_Char_JournalEntries_XML
This thread talks about changes to the API coming with Incursion 1.1.2 which isn't even deployed yet. Trying to use the functionality mentioned as coming in 1.1.2 and adding &rowCount=256 to the API call results in the server ignoring the beforeRefID parameter and returing the same page of data over and over.
So the rather obvious and seemingly unanswered question is: how on earth does wallet journal walking currently work, and where is that now documented? Is the API currently in any kind of usable state, and if not where is the service state of the API flagged as being offline so we are not all wasting our time trying to get something to function against an API which is still a work in progress? Are some parts of the API functional but not other parts, and again if so where is that indicated?
|
Catari Taga
Centre Of Attention Middle of Nowhere
|
Posted - 2011.01.26 12:31:00 -
[19]
Originally by: Neutrino Sunset Since the roll out of Incursion the behaviour of the API for walking the wallet journal has obviously changed, it used to return 1000 entries per call and now returns 50, breaking all code which uses it.
The documentation on this website here http://www.eveonline.com/api/doc/data-account.asp is now completely incorrect, as is the documentation here on Eve Dev http://wiki.eve-id.net/APIv2_Char_JournalEntries_XML
This thread talks about changes to the API coming with Incursion 1.1.2 which isn't even deployed yet. Trying to use the functionality mentioned as coming in 1.1.2 and adding &rowCount=256 to the API call results in the server ignoring the beforeRefID parameter and returing the same page of data over and over.
So the rather obvious and seemingly unanswered question is: how on earth does wallet journal walking currently work, and where is that now documented? Is the API currently in any kind of usable state, and if not where is the service state of the API flagged as being offline so we are not all wasting our time trying to get something to function against an API which is still a work in progress? Are some parts of the API functional but not other parts, and again if so where is that indicated?
If you had spent the time that went into this whine post reading the documentation you even linked I wouldn't be laughing at you now. --
|
Dragonaire
Caldari Corax. SOUL CARTEL
|
Posted - 2011.01.26 15:07:00 -
[20]
My question is when will WalletTransactions be moved to the new caching as well. It would be nice to have similar coding for both it and the journals again especially since the new system seems to work much better in many respects even though I've found the new cachedUntil useless since it's lying 90% of the time but not having as many API errors when things are just a little off is nice -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
|
|
|
CCP Stillman
|
Posted - 2011.01.26 16:57:00 -
[21]
Originally by: Dragonaire My question is when will WalletTransactions be moved to the new caching as well. It would be nice to have similar coding for both it and the journals again especially since the new system seems to work much better in many respects even though I've found the new cachedUntil useless since it's lying 90% of the time but not having as many API errors when things are just a little off is nice
It's not in our immediate plans for now, as far as I'm aware.
|
|
Dragonaire
Caldari Corax. SOUL CARTEL
|
Posted - 2011.01.26 20:52:00 -
[22]
One reason I ask is I seem at least personally to be getting only 101 error from transactions so thought it was maybe because of some change. I'll have to look into it some more now that I know there wasn't any changes -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
|
Block Ukx
Forge Laboratories
|
Posted - 2011.01.27 01:17:00 -
[23]
Edited by: Block Ukx on 27/01/2011 01:21:32
Originally by: Neutrino Sunset Since the roll out of Incursion the behaviour of the API for walking the wallet journal has obviously changed, it used to return 1000 entries per call and now returns 50, breaking all code which uses it.
The documentation on this website here http://www.eveonline.com/api/doc/data-account.asp is now completely incorrect, as is the documentation here on Eve Dev http://wiki.eve-id.net/APIv2_Char_JournalEntries_XML
This thread talks about changes to the API coming with Incursion 1.1.2 which isn't even deployed yet. Trying to use the functionality mentioned as coming in 1.1.2 and adding &rowCount=256 to the API call results in the server ignoring the beforeRefID parameter and returing the same page of data over and over.
So the rather obvious and seemingly unanswered question is: how on earth does wallet journal walking currently work, and where is that now documented? Is the API currently in any kind of usable state, and if not where is the service state of the API flagged as being offline so we are not all wasting our time trying to get something to function against an API which is still a work in progress? Are some parts of the API functional but not other parts, and again if so where is that indicated?
Had similar issue with my code. Change &beforeRefID= to &fromID=
BSAC Stock Exchange - EVE's only real-time stock exchange |
Ikaef Giasep
|
Posted - 2011.01.27 22:38:00 -
[24]
Hmm... the new spec in the wiki says:
"The journal is configured to provide up to 1536 entries or one week's worth of data."
Well, 1536 entries per 27 minutes max? This limit should be increased alot. Otherwise our corp would miss entries (which is really not good). The API should at least return all entries that were not returned with the previous API call. I consider this something to be fixed asap.
|
Catari Taga
Centre Of Attention Middle of Nowhere
|
Posted - 2011.01.27 23:06:00 -
[25]
Edited by: Catari Taga on 27/01/2011 23:07:06
Originally by: Ikaef Giasep Hmm... the new spec in the wiki says:
"The journal is configured to provide up to 1536 entries or one week's worth of data."
Well, 1536 entries per 27 minutes max? This limit should be increased alot. Otherwise our corp would miss entries (which is really not good). The API should at least return all entries that were not returned with the previous API call. I consider this something to be fixed asap.
You truncated that quote, I wrote "whichever is more". 1536 (or 6 pages) was the max I could pull past 1 week so that's what I wrote down, but I don't have a heavy trader at the moment so you should check how many you can pull and update the wiki, if necessary. --
|
Dragonaire
Caldari Corax. SOUL CARTEL
|
Posted - 2011.01.28 04:49:00 -
[26]
Edited by: Dragonaire on 28/01/2011 04:56:57 Just thought I'd let everyone know I've bug reported the issue with MemberSecurity and the cachedUntil tag being inside result instead of outside where it belongs ID# 106797
Ok barely had finished this post and got reply on bug.
Quote: Thank you for your bugreport - ID:106797 Title: MemberSecurity API cachedUntil misplaced. We are already aware of this problem, and have added your bugreport to the existing issue in our defect tracking system.
Nice response time on it much better than in the past when it might take weeks to hear back on anything to do with the API. This is such a welcome change.
-- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
|
|
Chribba
Otherworld Enterprises Otherworld Empire
|
Posted - 2011.01.28 11:12:00 -
[27]
Why was the API changed so that WalletJournal now says "DESC:" in before the text in the reason field?
/c
Secure 3rd party service | my in-game channel 'Holy Veldspar' |
|
Catari Taga
Centre Of Attention Middle of Nowhere
|
Posted - 2011.01.28 14:19:00 -
[28]
Originally by: Chribba Why was the API changed so that WalletJournal now says "DESC:" in before the text in the reason field?
/c
Yeah, is that a bug?
Originally by: Catari Taga Edited by: Catari Taga on 27/01/2011 23:07:06
Originally by: Ikaef Giasep Hmm... the new spec in the wiki says:
"The journal is configured to provide up to 1536 entries or one week's worth of data."
Well, 1536 entries per 27 minutes max? This limit should be increased alot. Otherwise our corp would miss entries (which is really not good). The API should at least return all entries that were not returned with the previous API call. I consider this something to be fixed asap.
You truncated that quote, I wrote "whichever is more". 1536 (or 6 pages) was the max I could pull past 1 week so that's what I wrote down, but I don't have a heavy trader at the moment so you should check how many you can pull and update the wiki, if necessary.
Btw since that was written for Incursion 1.1.1 and we now have the 1.1.2 changes I changed the wiki to "The journal is configured to provide up to one month worth of data.". As far as I understood CCP Stillman above, you can go back 1 month now regardless of how many transactions there are, but as I said, I'm not trading much anymore and cannot confirm. --
|
Dragonaire
Caldari Corax. SOUL CARTEL
|
Posted - 2011.01.28 14:23:00 -
[29]
From what I can tell by looking at one of the corps I'm in it is going back a month. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
|
Catari Taga
Centre Of Attention Middle of Nowhere
|
Posted - 2011.01.28 14:37:00 -
[30]
Originally by: Dragonaire From what I can tell by looking at one of the corps I'm in it is going back a month.
Yes, I was just wondering if there might be a cap on the number of transactions you can pull within that month, as with Incursion 1.1.0 there seemed to have been a hard cap of 1536. Unfortunately I only have about 900 transactions in the last month so I cannot confirm that now. --
|
|
|
|
|
Pages: [1] 2 3 :: one page |
First page | Previous page | Next page | Last page |