Edited by: Enraged Stoat on 18/06/2011 06:45:55
Calling the API repeatedly for the same data within any cache period should generate that yes, but I'm requesting the next page of data, not the same page.
My code gets the first page (by not specifying a beforeKillID), then (if the maximum 25 results were returned) requests the second page specifying beforeKillID. Should be able to walk through the pages within the same cache period. WalletTrans and WalletJournal both work this way, you can make repeated calls using fromID to walk through the data that is beyond the 2560 maximum entries per call. Requesting any page more than once within any cache period should generate the error, but I should not have wait for the timer to expire to request page 2 - that would mean a VERY long wait for all pages.
Thought I was following this wiki on Char_KillLog
to the letter "You can scroll back with the beforeKillID parameter listed below."
Is beforeKillID even the correct parameter to pass? If that's wrong the server thinks I'm requesting the same page. Can anyone confirm beforeKillID is what the API server is looking for in the request?