Jesús Leganés-Combarro

> Or as an alternative you could try @piranna 's fork #411 My fork is intended to have multiple queues in parallel, like multiple areas in the app, but my...

> But if you create N queues you could have them perform in parallel no? Yes, obviously, but just only one request at each time on each one of them,...

My company has sponsored me some changes and contributions to the project, so it would be cool :-)

> Hi @piranna Can we get some more info and example for this please. This appears to be quite a large feature. I'm also hesitant as we don't have any...

> I'm also hesitant as we don't have any tests around our updater either. I could be able to improve this is needed, too.

I don't have access to my company repo anymore, but I could be able to create a new pull-request from my personal account if needed. There's no need of any...

I've fixed the conflicts in #411, I think we can close this pull-request.

Fine! Can you point me where the discussion of v3 is about? :-)

> Could you pass me your email piranna? Yes, my professional account is [email protected]

In addition to that, a caching mechanism as proposed in https://medium.com/@d3byte/combining-indexeddb-with-redux-can-t-be-that-easy-f088fdeeb9bd would be nice, but probably it's out of scope, or current `redux-offline` could work already like that...