When it comes to Firestore caching using official web SDK, does it optimizes reads so it "sends" read request to the server only if the document changed after the last read? (so it doesn't generate 1 additional read of the document per attempt)
To elaborate a bit, consider the following scenario:
- user opens their profile page on the web app
- Firestore makes request to the server to fetch the profile document (1 read against pricing)
- user navigates away from the page and after a while returns back to the profile
- web app needs access to the profile document again
On the step 4. will Firestore request the document from the server by default even if it wasn't changed? (meaning it will count as 1 additional read against pricing every time user navigates to the profile page)
If yes, is it possible to configure Firestore so it only uses the cached object and only updates it when the object changed on server? How to do that?