You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
As discussed in the akka.js gitter room, here's a space where to discuss possible support for akka-persistence in scala.js.
The idea is to use localstorage or indexedDb as a backend, i have a use case where i need to save mouse event data locally when an app goes offline, and then stream them to a backend server once it's back online, for now i use akka-stream to handle buffer and throttling, and pouchdb to avoid using low level indexedDb api.
The text was updated successfully, but these errors were encountered:
It's awfully intriguing -- I'm not using akka.js myself yet, but in the long run this would be an argument in favor of my doing so.
I suspect that this will turn out to be most useful in the context of a larger framework, that wraps it with a concept of events flowing in both directions and a mechanism to use those events to update the local state. Certainly, I'd want a principled wrapper that has a concept of "persist these events over to the server, then flush them locally", to avoid building up dead events on the client side.
But yeah: this seems like a really useful tool towards an elegant client/server architecture that copes cleanly with the client being offline sometimes...
This is interesting indeed, and the use case totally justify the effort.
I will try to put together a starting point in these days if I find any spare time!
Hi,
As discussed in the akka.js gitter room, here's a space where to discuss possible support for akka-persistence in scala.js.
The idea is to use localstorage or indexedDb as a backend, i have a use case where i need to save mouse event data locally when an app goes offline, and then stream them to a backend server once it's back online, for now i use akka-stream to handle buffer and throttling, and pouchdb to avoid using low level indexedDb api.
The text was updated successfully, but these errors were encountered: