Since a little while back, the archives support ETag headers on the APIs. It would be good if the CF app could start using that, both because it will reduce load on the archives (particularly the message-id.json endpoint) and because the requests will be faster.
As a startingpoint, at least in refresh_single_thread() which keeps being called with the same arguments frequently. I think for that one the right thing to do is probably store the last seen ETag in a new column in MailThread and query on that.
Since a little while back, the archives support
ETagheaders on the APIs. It would be good if the CF app could start using that, both because it will reduce load on the archives (particularly the message-id.json endpoint) and because the requests will be faster.As a startingpoint, at least in
refresh_single_thread()which keeps being called with the same arguments frequently. I think for that one the right thing to do is probably store the last seen ETag in a new column inMailThreadand query on that.