3 ms·
This is a similar approach to what we're doing, except I went with Ractive for the view layer instead of React. How do you handle failed PUT/POST/DELETEs and c
by mikegioia 13y ago
This is a similar approach to what we're doing, except I went with Ractive for the view layer instead of React.
How do you handle failed PUT/POST/DELETEs and cases where the user is offline? This has been our biggest hurdle; mainly because when users feel like what they're using is a desktop app they think less about internet connectivity and assume the app should work offline (oy).
Currently I have the model save revisions of its data (one large document) through pouchdb but any solution with offline capabilities at some point needs to figure out conflict resolutions. I haven't got too far into conflicts/diffs but I'm curious if that's something you guys dealt with.
- skrebbel 13y agoWe don't really deal with it at all yet. Good warning! That said, given the nature of our app, I think that for us, displaying an error bar on top and caching the last PUT/POST/DELETE in a slow retry loop is probably enough - it's a content-heavy app, so people will understand that the content comes from the internet. I hope. :-) So, in short, you're ahead of us here.