| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Rhennthyl
NordEste Trading
1
   |
Posted - 2012.06.29 17:59:00 -
[1] - Quote
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? |
Rhennthyl
NordEste Trading
1
|
Posted - 2012.06.29 19:31:00 -
[2] - Quote
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 :) |
Rhennthyl
NordEste Trading
2
|
Posted - 2012.07.05 12:45:00 -
[3] - Quote
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. |
Rhennthyl
NordEste Trading
2
|
Posted - 2012.07.05 14:27:00 -
[4] - Quote
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 :) |
| |
|