Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Zylinda
Enlightened Industries Test Alliance Please Ignore
0
|
Posted - 2012.04.02 13:33:00 -
[1] - Quote
I'm using PHP to retrieve data via the Eve API. Whilst most of the pages work as expected, I'm having issues pertaining to the kill log.
When I do a FIRST call to "KillLog.xml.aspx", I get an expected response, with kill details. However, if I call the same page subsequently, I get:
"Eve API" wrote:< eveapi version="2" > < currentTime >2012-04-02 13:21:31< /currentTime > < error code="119" > Kill log exhausted (You can only fetch kills that are less than a month old): New kills will be accessible at: 2012-04-02 14:17:09. If you are not expecting this message it is possible that some other application is using this key! < /error > < cachedUntil >2012-04-02 14:17:09< /cachedUntil > < /eveapi >
I've tried using the optional parameter "beforeKillID" (with both valid and text values) but this doesn't appear to do anything (that I can make work)
Does this call 'empty' the kill log list? Is there not a way to retrieve the data again? (ie if a fault occured?)
|
Khorkrak
War Tribe
2
|
Posted - 2012.04.02 14:55:00 -
[2] - Quote
Good question as I was experiencing the same thing. I ended up deleting the key I was using and I created a new one. Worked fine right away. Before doing that though I'd tried waiting a few times until after the date and time specified in the error message to retry but always received that weird error message.
What's this beforeKillID parameter? Something related to the EDK Killboard IDfeed? This will just be ignored by the EVE API if so. Extraordinary claims require extraordinary evidence |
Zylinda
Enlightened Industries Test Alliance Please Ignore
0
|
Posted - 2012.04.02 17:28:00 -
[3] - Quote
It's the one listed on the http://wiki.eve-id.net site here: http://wiki.eve-id.net/APIv2_Char_KillLog_XML
I've tried using different keys, but each time it just lets it be called once, then shows the error message any time after. |
Artemus Black
State War Academy Caldari State
0
|
Posted - 2012.04.03 20:57:00 -
[4] - Quote
I'd like to know the answer to this one! |
Khorkrak
War Tribe
2
|
Posted - 2012.04.03 21:18:00 -
[5] - Quote
Yep same nonsense for me - even with different keys. I don't understand this. Extraordinary claims require extraordinary evidence |
Equto
EXURO VITA GREATER ITAMO MAFIA
11
|
Posted - 2012.04.03 21:38:00 -
[6] - Quote
I have been wondering the same thing. |
Zylinda
Enlightened Industries Test Alliance Please Ignore
0
|
Posted - 2012.04.04 15:10:00 -
[7] - Quote
After a bit of playing, I'm pretty sure this API is bugged as it certainly acts differently from all the other calls.
With any given key, when you make a first call to KillLog.xml.aspx, it will give you a list of the previous kills. It says up to a month, but if there aren't many kills, it will actually go back a LOT further than that, so perhaps it is actually just a max number of kills it returns.
After that, the call just returns an error message, even with the optional beforeKillID parameter
However, one hour later, the call will again return the full list of kills, once, before returning an error again.
Really irritating! |
Dragonaire
Corax. The Big Dirty
36
|
Posted - 2012.04.04 15:36:00 -
[8] - Quote
Zylinda wrote:After a bit of playing, I'm pretty sure this API is bugged as it certainly acts differently from all the other calls.
With any given key, when you make a first call to KillLog.xml.aspx, it will give you a list of the previous kills. It says up to a month, but if there aren't many kills, it will actually go back a LOT further than that, so perhaps it is actually just a max number of kills it returns.
After that, the call just returns an error message, even with the optional beforeKillID parameter
However, one hour later, the call will again return the full list of kills, once, before returning an error again.
Really irritating! In other words it's work exact like it is suppose to and you are ignoring the cachedUntil timer. CCP has changed some of the APIs to allow you to re-get the last data on some APIs but just because they sometimes allow it on some APIs doesn't mean you should expect to on them all. I know it can be confusing when they mess up the cachedUntil time they return in the returned data for new developers but you really need to obey the expected cache times which for killLogs is 1 hour. The problem with bad cachedUntil times in the XML finally drove me to using currentTime and a DB table to figure out the correct time myself in Yapeal. You can find the intervals in the utilCachedInterval table now from Yapeal.
Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Etil DeLaFuente
New Eclipse Initiative Mercenaries
4
|
Posted - 2012.04.06 01:50:00 -
[9] - Quote
I find it quiet annoying too,
if a third party already called the api with another key, you won't get the kills.
I can understand the need to reduce the load on ccp servers however, that behavior should be applied per key.
|
Desmont McCallock
155
|
Posted - 2012.04.06 06:00:00 -
[10] - Quote
Same things goes for the ContractBids API call. Although I have reported it and mentioned it directly to CCP staff via irc channel, no action has been taken yet. That design patterns has many defects. CCP won't realize that and won't do nothing until this becomes an outcry.
I can only think of one solution: Jita protest. |
|
Etil DeLaFuente
New Eclipse Initiative Mercenaries
4
|
Posted - 2012.04.06 14:42:00 -
[11] - Quote
Desmont McCallock wrote:I can only think of one solution: Jita protest.
Let's start with petition first |
Desmont McCallock
155
|
Posted - 2012.04.06 17:11:00 -
[12] - Quote
Etil DeLaFuente wrote:Desmont McCallock wrote:I can only think of one solution: Jita protest. Let's start with petition first
Good luck with that. |
Ydnari
Estrale Frontiers Project Wildfire
117
|
Posted - 2012.04.06 19:34:00 -
[13] - Quote
Etil DeLaFuente wrote:I find it quiet annoying too,
if a third party already called the api with another key, you won't get the kills.
I can understand the need to reduce the load on ccp servers however, that behavior should be applied per key.
AARGH
Suspected that might be why I never get any kills showing up on one key, this just confirms it.
Makes a mockery of the error message since that says it's per key not per account... |
Etil DeLaFuente
New Eclipse Initiative Mercenaries
4
|
Posted - 2012.04.07 05:22:00 -
[14] - Quote
Petition sent, let's see how long it takes to get a response :) |
Etil DeLaFuente
New Eclipse Initiative Mercenaries
4
|
Posted - 2012.04.10 02:14:00 -
[15] - Quote
You can only use one key per account.
So, if multiple third parties need to access the killlog, you have to provide a different key from a different account each time.
|
Desmont McCallock
158
|
Posted - 2012.04.10 06:13:00 -
[16] - Quote
That sucks. Diff key I understand. But why diff account? (rhetorical question) |
Milo Caman
Anshar Incorporated
34
|
Posted - 2012.05.17 18:18:00 -
[17] - Quote
Bit of a Necro, but has anyone managed to resolve this?
If not, can you seriously not have multiple corporate keys pulling kills to different places? (I.E. Key for EVE-Kill, Key for personal Killboard) |
Artctura
Clan Shadow Wolf Fatal Ascension
9
|
Posted - 2012.05.25 19:53:00 -
[18] - Quote
This is seriously, one of the things that amazes me was not fixed with the new API system. I can't think of a reason why this isn't technologically simple, but it is an absolute pain when your trying to keep track of multiple director API's for a kill board. I need to watch logs, stagger pull times and do all sorts of other stuff because this is a "BY CHARACTER" issue.
I can understand it being by key, I can't understand it being by character. It's almost as if someone put the wrong field in the code somewhere. |
Desmont McCallock
179
|
Posted - 2012.05.25 20:42:00 -
[19] - Quote
And this is the reason why EVEMon can't have a Kill Reports monitor. It's been two expansions now and I feel so neglected. |
Khorkrak
War Tribe
3
|
Posted - 2012.05.26 16:47:00 -
[20] - Quote
This is pathetic on CCP's part. Along with the 1 month / 100 kill mails limit. What?! Great so only old sites get a monopoly on verified kills. Come on... The coupe de grace is the complete abscence of a way to even dump your own combat log to a file from the client. Extraordinary claims require extraordinary evidence |
|
Etil DeLaFuente
New Eclipse Initiative Mercenaries
8
|
Posted - 2012.05.27 09:53:00 -
[21] - Quote
Desmont McCallock wrote:And this is the reason why EVEMon can't have a Kill Reports monitor. It's been two expansions now and I feel so neglected.
Use EveKill API like the rest of us. Their new EPIC api is quiet good. |
Etil DeLaFuente
New Eclipse Initiative Mercenaries
8
|
Posted - 2012.05.27 09:59:00 -
[22] - Quote
Artctura wrote:This is seriously, one of the things that amazes me was not fixed with the new API system. I can't think of a reason why this isn't technologically simple, but it is an absolute pain when your trying to keep track of multiple director API's for a kill board. I need to watch logs, stagger pull times and do all sorts of other stuff because this is a "BY CHARACTER" issue.
I can understand it being by key, I can't understand it being by character. It's almost as if someone put the wrong field in the code somewhere.
Well, i petitioned it, got a "by design" response. Maybe if everyone pissed by this "poorly thought design" petition it, ccp might actually change something. (or not) |
Desmont McCallock
179
|
Posted - 2012.05.27 10:11:00 -
[23] - Quote
Etil DeLaFuente wrote:Desmont McCallock wrote:And this is the reason why EVEMon can't have a Kill Reports monitor. It's been two expansions now and I feel so neglected. Use EveKill API like the rest of us. Their new EPIC api is quiet good. I don't like EVEMon being depended on another service, except of course CCP's API (data provider) and BattleClinic (host). No offence to Karbowiak for creating it. |
Etil DeLaFuente
New Eclipse Initiative Mercenaries
8
|
Posted - 2012.05.27 10:29:00 -
[24] - Quote
Desmont McCallock wrote:Etil DeLaFuente wrote:Desmont McCallock wrote:And this is the reason why EVEMon can't have a Kill Reports monitor. It's been two expansions now and I feel so neglected. Use EveKill API like the rest of us. Their new EPIC api is quiet good. I don't like EVEMon being depended on another service, except of course CCP's API (data provider) and BattleClinic (host). No offence to Karbowiak for creating it. And for clarification EVEMon doesn't store the data it retrieves and it's design philosophy is not to use a DB.
It all depends on the benefits your users could get from such a feature. Having to rely on a third party is not so important if the benefit is high. And i suspect evekill is not going to die anytime soon. Look for instance dotlan, if i'm not mistaken, it uses evekill api pretty much in the same way you'd do.
but, i totaly agree that CCP should provide it first. |
Artctura
Clan Shadow Wolf Fatal Ascension
9
|
Posted - 2012.05.28 17:03:00 -
[25] - Quote
Etil DeLaFuente wrote:Artctura wrote:This is seriously, one of the things that amazes me was not fixed with the new API system. I can't think of a reason why this isn't technologically simple, but it is an absolute pain when your trying to keep track of multiple director API's for a kill board. I need to watch logs, stagger pull times and do all sorts of other stuff because this is a "BY CHARACTER" issue.
I can understand it being by key, I can't understand it being by character. It's almost as if someone put the wrong field in the code somewhere. Well, i petitioned it, got a "by design" response. Maybe if everyone pissed by this "poorly thought design" petition it, ccp might actually change something. (or not)
But why is it even by design. I can't understand the technical limitation here. The API simply reports the last 100 kills and can be walked backwards, presumably to 0, but at least 30 days in the past. It returns less than 100 kills if that is all there were in the last 30 days.
What specifically here requires that there only be 1 external api client hitting this per CHARACTER? |
Desmont McCallock
179
|
Posted - 2012.05.28 18:20:00 -
[26] - Quote
The fact that the API call was designed when there were limitations and is abandoned since. |
Dedaf
United Brothers Of Eve Seventh Sanctum.
39
|
Posted - 2012.06.03 09:24:00 -
[27] - Quote
I have had the very same problem. It seems to be true whats being posted here, that you can only have 1 killLog API key per character. I had 3 API keys for different tools that i use, and i had put mark in all 3 keys to fetch killLog. After removing the killLog marker from the 2 other keys, then it works. So now the only API key with a mark in killLog is the one i use for the killboard and now it updates fine. But i guess for you guys who need kill logs for other tools than just the killboard, then it sucks. Hope they will fix this. |
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |