2
In an application with React Native, using Redux and Redux-Persist, how best to identify which content needs to be updated?
In my case, I have an app that makes some requests at start up.
When I enabled the redux-persist I avoided the requisition if it had already been made at another time. But I have no idea how best to identify now whether or not to release the request again to update the data stored by redux-persist.
I read about using ETags and Last-Modified, but this implies implementing this in the API also correct?
Some guidance to get this functionality implemented in the right way?
well complicated because it will depend a lot on your application and the data required at the time, eg normally profile data need a lower refresh frequency. To solve it can put a boot of refresh where it is necessary.
– Neuber Oliveira
I thought of putting a Reset pulley in these places where the data does not undergo direct update. These I can keep in cache for a long time, but the data that is constantly updated, I see no other way than to save something that indicates the last change. So I was wondering if anyone had ever done anything like that.
– Luciano Lima