Last change timestamp
ezd.6359:
I asked for it long ago but…
I think it will be good if you will add timestamp key for every api item.
Why?
For example, if you change one random ingame item (typo or smth), we need to update our database. Should we retrieve ALL data? It is not a good idea. We dont even know if you changed something. Should we pull everything everyday?
Is not it better just to check timestamp only?
Two ways:
1) items/last_updates?ids=…
return
{
“1234”: 0123456789, // item_id: unix_timestamp
“555”: …
}
2) items/changes?since=0123456789
return
[1234,555,6666]
- We will be sure our db is fresh and actual
- We can update only specific items/colors/recipes etc
P.S. It is not about “items” only, it is about all.
Lawton Campbell.8517:
There’s no way for us to implement this on our end — the server that reads the dat file does not have the capability to persist any data, and the dat file has no notion of changes. Implementing this would require significant architectural changes across multiple components (read: 4+ months of me working on it).
The good news is that because we’re reading it from the dat file, exposed data only changes when there’s a patch — so you only need to do a full reindex when /v2/build changes. Otherwise you can just watch the list of ids and pull the new ones daily.