Providing an offline strategy

[jorishermans]

When the connection is lost with the server, we are going to store all the socket events into websql or localstorage. Whenever the connection is back established the events will be fired in the same order. So you can bring the state of the client back in order with the server.

We will use Cargo for this.

[cgarciae]

Cool! I was thinking about that as I watched the video. Have you seen MeteorJS? They do something similar, but on top of web socket "offline strategy" they directly expose a MongoDB API to the client, then they have some angular-like system to update templates, results in really magical stuff.

With a client DB API + "offline strategy" + integration with AngularDart you could get the same AWSOME effect.

[cgarciae]

I see that you have bigcargo. Does it work on the browser? If not, any plans on exposing an API to the client? Something like that could make basic data fetching + syncing a TRIVIAL task on the client. Manipulating the data on the client-side is a liberating experience.

[jorishermans]

I like your idea of a client DB API! I will create another issue about that! Where we can fill in some suggestions about how the db api should look like. For the moment you can look at my part 2 video, but indeed that requires some dumb programming on the server that can be taken away. I also prefer to base myself on an abstraction layer then directly to mongoDB, because then you force your users to use that, now they can also use redis and in the future google datastore, memcache, ...

With this feature I want to store the message events in localstorage and when there is a connection again the events will be fired to the server.

[cgarciae]

Great! I will certainly contribute some ideas to the list. Mean while, if you dont know meteor, check them out for some inspiration.