open All Channels
seplocked EVE Technology Lab
blankseplocked Cache until time in error results causes API to be hammered
 
This thread is older than 90 days and has been locked due to inactivity.


 
Author Topic

Desmont McCallock
Posted - 2011.08.18 10:39:00 - [1]
 

@CCP Elerhino & CCP Stillman or whoever this concerns.

Bug report ID: 115692.

Cache until on every API error result is same as current time resulting to possible API server hammering.

CCP Stillman

Posted - 2011.08.18 13:27:00 - [2]
 

I can't see that. Depending on the error, it returns for instance 12 hours in some instances, 24 in others.

Are you sure it isn't just that you're getting a 24 hours cachedUntil timer back?

Desmont McCallock
Posted - 2011.08.18 13:54:00 - [3]
 

Edited by: Desmont McCallock on 18/08/2011 13:56:12
Originally by: CCP Stillman
I can't see that. Depending on the error, it returns for instance 12 hours in some instances, 24 in others.

Are you sure it isn't just that you're getting a 24 hours cachedUntil timer back?


Just hit on the link.

Getting the same cache until time on error "211", which actually caused EVEMon to spot the bug.

Callean Drevus
Caldari
Icosahedron Crafts and Shipping
Silent Infinity
Posted - 2011.08.18 16:56:00 - [4]
 

Can confirm I see it too.

Dragonaire
Caldari
Corax.
PURgE Alliance
Posted - 2011.08.20 05:33:00 - [5]
 

I've been ignoring the cachedUntil time on errors for months if not years now because they have been useless with the exception of the ones in the actual message. With the new ones I've seen someone from CCP say that for the different classes (100s, 200s, etc) they should have some kind of really stupidly long cache times. I would say they are even more useless than before as it makes no sense to have to wait 12 hours or more because of a bad packet causing error to be returned when the next time the API returns everything fine. On any error I just wait 10 minutes and try again but if there is an actual time inside the message returned I'll use it as long as it's longer than 10 minutes as well Wink

Actually the cachedUntil time has become mostly useless even when there isn't an error because most the time it tells you it's fine to call again in 5 minutes and when you do then you get an error to wait longer or you just get the same data again because it hasn't updated which is a terrible waste of bandwidth IMHO. It would make so much more sense to have it return current time plus the actual data refresh time to all callers. This would also tend to keep multiple applications from group together and causing load spikes which return wrong chachedUntil times now causes.

Desmont McCallock
Posted - 2011.09.02 11:58:00 - [6]
 

Any update or info on when this bug will get fixed?

Although I can programmatically get around it, I prefer the bug fix.

Thanks in advance.


 

This thread is older than 90 days and has been locked due to inactivity.


 


The new forums are live

Please adjust your bookmarks to https://forums.eveonline.com

These forums are archived and read-only