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.
 

Killog error 120
Author
Previous Topic Next Topic
nicegirl2
Hedion University
Amarr Empire
#1 - 2012-02-18 11:51:54 UTC
Rigth after first call i get :

Quote:
Expected beforeKillID [XXXXXXXXX] but supplied [0]. Please supply the expected killID! If you are not expecting this message it is possible that some other application is using this key!


Okay someone using that key aswel thats rigth. why cant we get a cached results?


Next issue a less more issue but an issue anyway.

If i provide beforeKillID as lowest killID from seccessful parsing of xml, anyway i get same error, expect beforkil blah blah blah. And expected kill id less that 100000 then ID i providing. its no way it can be such big diference betwen them.

why, Why, wHy, WHY is that so? is that broken or i doing somsn wrong? but i cant get what exacly, its no way to screw simple URL call...
Trenker
#2 - 2012-02-18 18:08:50 UTC
nicegirl2 wrote:
Rigth after first call i get :Okay someone using that key aswel thats rigth. why cant we get a cached results?


[url]http://wiki.eve-id.net/API_Cache_Styles#Long_Cache_Style[/url]

nicegirl2 wrote:
If i provide beforeKillID as lowest killID from seccessful parsing of xml, anyway i get same error, expect beforkil blah blah blah. And expected kill id less that 100000 then ID i providing. its no way it can be such big diference betwen them.


Please write proper sentences, it's difficult to understand what you are talking about.

Since the error is the same, its source is the same: some app tried to call that URL before. Request a unique keyID and vCode pair for your app, that's much less painful and safer!
nicegirl2
Hedion University
Amarr Empire
#3 - 2012-02-19 16:35:33 UTC
Trenker wrote:
nicegirl2 wrote:
Rigth after first call i get :Okay someone using that key aswel thats rigth. why cant we get a cached results?


[url]http://wiki.eve-id.net/API_Cache_Styles#Long_Cache_Style[/url]


Thank you, i know that. i was just wondering why its made so illogical. now i need 2 or more keys for diferent web sites, why cant ccp just update killog once per hour and give it to all queries? it will lower load on server and make our lifes much esear...



Trenker wrote:

nicegirl2 wrote:
If i provide beforeKillID as lowest killID from seccessful parsing of xml, anyway i get same error, expect beforkil blah blah blah. And expected kill id less that 100000 then ID i providing. its no way it can be such big diference betwen them.


Please write proper sentences, it's difficult to understand what you are talking about.

Since the error is the same, its source is the same: some app tried to call that URL before. Request a unique keyID and vCode pair for your app, that's much less painful and safer!


ok, sorry. second try.

i get first results from killog and parsed it, saved lower killid, and now making second api query, with that saved id. and server telling me that same 120 error. and its saying like "u provided me beforeKillID=X but i need X-100 000", why is it so? why it so much less then last id in previuos call?
Dragonaire
Here there be Dragons
#4 - 2012-02-20 02:22:18 UTC
First are you sure you are using the lowest ID received or are you assuming the first or last one in the XML is it? The reason I ask is because the result is not sorted coming from the API server. I just noticed that my code in Yapeal made this assumption and fixed it like I'd already done with WalletJournal and WalletTransactions.

Second you need to check if the number of rows received match the number requested. If it's less you're done.

Lastly you should check if the date of the oldest kill you received is less then a week old since you can only walk back for the last week.

Finds camping stations from the inside much easier. Designer of Yapeal for the Eve API. Check out the Yapeal PHP API Library thread.
nicegirl2
Hedion University
Amarr Empire
#5 - 2012-02-20 12:13:47 UTC
the code is from EDK board api killog plugin:

Quote:


foreach($sxe->result->rowset->row as $row) {
if($currentkill < (int)$row['killID']) {
$currentkill = (int)$row['killID'];
}
}



so i asume its working ok.

dates ar ok aswel. i checked.


Quote:
Second you need to check if the number of rows received match the number requested. If it's less you're done.


is ther a way to specify how much rows i want to get from ccp api? i just request url first whitout befourID, and then with it. and on second time i get 120 error. ok i get from message which id it want, pass it as beforID, its works, i get page of kill, i parsing them, and store lowest ID again. again trying to pass it - get 120 error again, etc etc etc...


its not a problem realy becose actual kills amost never get from the first page call. but its bother me. its so inacurate...
Dragonaire
Here there be Dragons
#6 - 2012-02-22 17:44:03 UTC
You can't set the number you request like with some of the other APIs but you do get a set number each time if there are enough kills. You will receive a max of 25 for char version and 100 for corp as noted on http://wiki.eve-id.net/APIv2_Char_KillLog_XML

Finds camping stations from the inside much easier. Designer of Yapeal for the Eve API. Check out the Yapeal PHP API Library thread.