A5308Y commented 6 years ago

Possible Solutions

CRDTs

Seems to be the "correct" solution. Is this memory intensive? Possible Implementations:

Elm SEQ. Not updated for 0.19 yet, Not production ready, Is it active?
Automerge. Every interaction has to go through a port? JS is dangerous?
Hypermerge
https://github.com/Zinggi/NoKey/tree/master/web/lib/Crdt
Write my own

Everything manually

When to save to localStorage?

Save on every interaction?
on every save button click?

When to save to server?

On "synchronization"-click?
Every x minutes?

Scenario:

Client 1 checks off an action offline Client 2 renames the same action offline Client 1 goes online and saves its action What happens?

A5308Y commented 6 years ago

Implemented a working version that's fast enough and does not exceed maximum stack size. Needs some work before I feel comfortable including it in Methodoly though.

julianpistorius commented 5 years ago

Implemented a working version that's fast enough and does not exceed maximum stack size. Needs some work before I feel comfortable including it in Methodoly though.

Hi @A5308Y. This sounds intriguing. I've been investigating using CRDTs in Elm for syncing. Are you open to sharing your initial working implementation on GitHub?

A5308Y commented 5 years ago

Sure. I put it up at https://github.com/A5308Y/elm-crdt there are still edge cases that need to be addressed. I'd be happy to have a short call about this if you're up for it.

julianpistorius commented 5 years ago

Great! Thank you for the offer - I think I'll take you up on that.

I'll try it out first and get back to you with questions.

A5308Y / Methodoly

Effortless synchronization #46