Timeline for reduce api calls - please add last_modified to user structure
Current License: CC BY-SA 2.5
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 18, 2010 at 14:35 | comment | added | Edan Maor | Thanks, I didn't know that. I'll have a look at that now. | |
| Jun 18, 2010 at 13:37 | comment | added | Kevin Montrose |
@Edan Maor - that can be accomplished by sorting by creation (for new answers, or activity for new and changed answers), and setting min to the last query time. Variations on that approach allow for caching in a number of use cases.
|
|
| Jun 18, 2010 at 12:22 | comment | added | Edan Maor | How about adding a way to query "last modified" on lists? For example, in Stack2Blog (stackapps.com/questions/611/…), we need to grab a user's entire list of answers. If we want to implement caching, it would be helpful to query whether or not the list of answers has changed (I assume this applies in other places as well). | |
| Jun 18, 2010 at 8:46 | vote | accept | Sky Sanders | ||
| Jun 18, 2010 at 8:46 | comment | added | Sky Sanders | granted. who churns their profile?. creation is enough info to pull just users created later than the last time your cache was updated. hooking last_modified, when/if it exists, would be nice. Thanks. | |
| Jun 18, 2010 at 8:30 | history | answered | Kevin Montrose | CC BY-SA 2.5 |