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.
 

Cache timers on CAK keys
Author
Previous Topic Next Topic
Rhennthyl
NordEste Trading
#1 - 2012-06-29 17:59:41 UTC
Just to confirm my own assumptions, cache timers are not specific to the CAK keyID for character and corporation pulls but are shared between different keys that are pulling the same character/corp data.

For example, if I created two different keys that both included the AssetList accessmask for Rhennthyl, they would both be constrained by a single timer, not by two independent timers, correct?
Acid Kanshi
AIFAM
#2 - 2012-06-29 19:18:34 UTC  |  Edited by: Acid Kanshi
Correct. At least that is what I do. Cache timers are characterID/corpID specific for each call.

If you loop through 10 keys, all contain same characterID in them. Then it will query the API on first step, other 9 steps will use local data already and won't query the API.

EVE-Cost is a manufacturing tool for EVE players. http://www.eve-cost.eu
Rhennthyl
NordEste Trading
#3 - 2012-06-29 19:31:41 UTC
Can anyone confirm whether pulls from the corporation API pages are cached specifically to the characterID supplied or to the corporation ID? Considering that they take the characterID of one of the directors as their input, I sort of see it as an open question and I don't really want to move characters around to test it :)
Osku Rei
Pixel 6
#4 - 2012-07-03 16:15:41 UTC
Rhennthyl wrote:
Can anyone confirm whether pulls from the corporation API pages are cached specifically to the characterID supplied or to the corporation ID? Considering that they take the characterID of one of the directors as their input, I sort of see it as an open question and I don't really want to move characters around to test it :)


I would also very much like to know this :)

Next generation of lottery tracker coming soon! http://evelotterytracker.com/

Please like my post if it has helped you :)
Scoota 2
State War Academy
Caldari State
#5 - 2012-07-03 16:27:52 UTC  |  Edited by: Scoota 2
Rhennthyl wrote:
Can anyone confirm whether pulls from the corporation API pages are cached specifically to the characterID supplied or to the corporation ID? Considering that they take the characterID of one of the directors as their input, I sort of see it as an open question and I don't really want to move characters around to test it :)


Agreed, Quite an important issue for me as well

Also, since it is relevant to the original question, what about an instance where a character queries "/char/CalendarEventAttendees.xml.aspx", where the eventIDs argument must be passed. Are we forced to query all events for that character in one go or can we query the server multiple times for separate events?
Jack Arc
Deep Core Mining Inc.
Caldari State
#6 - 2012-07-03 17:17:21 UTC  |  Edited by: Jack Arc
Each corp API call is bound to the characterID that calls it, as you can only call a corp API call from a character which is a CEO or Director. Therefore a corp API call can be made without using the characterID parameter.
Exception is the CorporationSheet API call as it can also be called providing only the corporationID which returns limited corp info.
Scoota 2
State War Academy
Caldari State
#7 - 2012-07-03 17:28:59 UTC
from a logical perspective id say they are cached to a characterID. If they where not a director would not be able to pull long cache style data if the ceo has just done so.

In the reverse a characterID would only ever have one corporation, and since api pages seem to be cached per characterID per api page it would make sense
Dragonaire
Here there be Dragons
#8 - 2012-07-05 04:16:59 UTC
sense != Eve API Blink if you haven't figured that out yet you will.

Finds camping stations from the inside much easier. Designer of Yapeal for the Eve API. Check out the Yapeal PHP API Library thread.
Rhennthyl
NordEste Trading
#9 - 2012-07-05 12:45:20 UTC
Jack Arc wrote:
Each corp API call is bound to the characterID that calls it, as you can only call a corp API call from a character which is a CEO or Director. Therefore a corp API call can be made without using the characterID parameter.
Exception is the CorporationSheet API call as it can also be called providing only the corporationID which returns limited corp info.


I kept reading the sentence with the highlighted word before I realized that you probably meant corporationID, which should indeed be extraneous if you have already supplied the characterID of a director.

Let me know if I'm reading this wrong.
Jack Arc
Deep Core Mining Inc.
Caldari State
#10 - 2012-07-05 14:12:05 UTC  |  Edited by: Jack Arc
I mean characterID. When calling a corp API with Legacy key, you have to use characterID too, which is now optional with CAK key.

What may confused you is the 'exception' sentence, as the CorporationSheet can also be called without the CAK credentials and by providing only the coprorationID to get a limited version of the corp info.
When using Legacy key, you have to provide the characterID in order to get the full corp info.
Rhennthyl
NordEste Trading
#11 - 2012-07-05 14:27:34 UTC
I went back to the key creation screens and now I see what my disconnect was.

I had forgotten that corporation CAKs have to be created separately from character CAKs and that the keyIDs already correspond one to one with a corporation and character in that case. I was operating under the assumption that the CAKs I had created for character API calls, which have the ability to span multiple characters on my account, could also have the accessmasks for the corporation API calls added to them too. Now I see that's not possible, so both the corporationID and characterID parameters are moot, except in the case that you already listed.

Thanks :)