Originally Posted by antihax
[*] What about duplicates?
The developer receiving the data is responsible for handling duplicates; the uploader will intentionally send duplicate data. So far I have found that rounding some of the timestamps to 10 help resolve the off by one or two issues and have other identifiers to handle most duplicates. Help here to simplify this would be appreciated.[/list]
|
If I were to implement this
-- and I was pondering that idea, but wasn't enough into trading to take on such an enormous task 
certainly not since two trading guilds I was in died overnight with ESO update 3 or 4 -- I'd start with a request for ZOS to add SaleId to every store-related API (search, listing, history). The client must have it, it's just a matter of passing it to add-ons. Then there would be no issues with duplicates.
Even replacing the "timeRemaining", "secsSinceEvent" and similar parameters with solid timestamps would simplify detection of duplicates.