Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Ryzlan
|
Posted - 2009.07.04 05:42:00 -
[1]
Hi all,
I'm writing a script in Python that downloads my market transactions. When I pass it a beforeTransID = 0 initially and then walk back to the last seen ID, I randomly get "Expected before ref/trans ID = 0: wallet not previously loaded." messages. Not always, but I'd say every 1 in 3 times I try to pull the full amount of data, I'm getting this. Does this have anything to do with the serverside playing catch up as to what i've downloaded? Please tell me I'm not the only one encountering this on a regular basis.. I've been picking my brain here for hours trying to figure out what's going on here.
Thanks.
|
Dragonaire
Caldari Corax.
|
Posted - 2009.07.04 06:13:00 -
[2]
I found when developing Yapeal that I had to add a 1-2 sec delay between pulls when doing that or I would get the error often It seems if you don't the API servers get confused about what you have already got and think you're out of sequence on your requests -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
|
Ryzlan
|
Posted - 2009.07.04 06:18:00 -
[3]
Do you still get the errors from time to time with yapeal? Because i've been tinkering with delaying it as well, but by large amounts.. maybe delaying it too long is bad too?
|
Hel O'Ween
Academy of Truth
|
Posted - 2009.07.04 10:45:00 -
[4]
Quote:
When I pass it a beforeTransID = 0 initially and then walk back to the last seen ID,
Make sure you pass the lowest refID to subsequent requests, not the last one.
Ideally, these should be the same, but better be safe than sorry. -- EVEWalletAware - an offline wallet manager |
Dragonaire
Caldari Corax.
|
Posted - 2009.07.04 17:26:00 -
[5]
Too long also causes problems and yes to do it right should look for the lowest but in all my testing it was always the last one so I took the easy way out and just grab the last one and it's date as well and if it's more than a week ago I know it's time to stop else I try with that ID. Any errors returned by the API throw an exception in the code and it goes on to the next API. Normally Yapeal doesn't seem to log more than 1-2 errors a day with the current 2 sec delay and then only around downtime for the API servers or when they aren't working right. -- Finds camping stations from the inside much easier. Designer of Yapeal for Eve API.
|
Ryzlan
|
Posted - 2009.07.05 06:16:00 -
[6]
Just as a follow up, I found my problem. I was opening new http connections with every API call and that was causing the errors. Keeping just the one socket open until it's done works just fine. Now I'm happy. :)
|
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |