Keep synced for connection losts about choo-persist HOT 3 OPEN

Seems like wrapping xhr at the application level and then hooking that to some sort of queue backed by choo-persist could be interesting. It'd be really cool if this wasn't xhr specific, lots of folks are doing rpc over a websocket. Maybe modeling this feature after an elm effect manager would allow it to be separated from the actual transport.

from choo-persist.

Interesting; this is def worth trying out I think.

Hmmm, I believe there's a built-in option in indexedDB to catch all requests while offline so they can be replayed, at the XHR level. Might be worth digging into.

I wonder if it wouldn't be easier to wrap xhr and prep it for replayability, as that might provide more control. Not sure; this is definitely worth experimenting with.

from choo-persist.

Exactly, in fact, even for my use case, keeping this feature xhr relative is an issue. The best approach would be to leave all the work for choo hooks and wrappers. It could also be done by checking connectivity before getting any error. And using the same check, to sync data to the network when connection is availaible again. To make it more network agnostic, the user should provide a sync function so not only xhr is supported.

from choo-persist.