Like oh-so-many things, I implemented this about 1.5 years ago now. I even gave 2 talks on it. With Elm 0.17, you can implement it in under 30 lines of code, using firebase as a host. Sadly, the recordings of both the talks I gave on it are lost. But you can read it here -> https://github.com/eeue56/talks/tree/master/experiments_in_elm#the-future-of-debugging-with-elm
On Fri, Mar 3, 2017 at 7:15 AM, Zachary Kessin <[email protected]> wrote: > No but that would be a really cool idea, I can think of several places > that this could be useful, for example checking that things work the same > on all browsers. Or being able to generate a sequence of events from a > quickcheck type thing and play them in a browser. > > Zach > ᐧ > > On Thu, Mar 2, 2017 at 5:57 PM, 'Rupert Smith' via Elm Discuss < > [email protected]> wrote: > >> Anyone tried something along these lines: >> >> The state of an application in Elm can be re-built by starting from its >> 'init' state, then replaying all messages to a given state. This is called >> event sourcing. >> >> If I am using some application written in Elm, and I want to share what I >> am doing with someone else, all I need is for them to start up the same >> application, the replay my event stream over it. Something like AMQP over >> Web Sockets could provide the transport layer. >> >> There might need to be a way on the slave application to ignore all of >> the local users events, and only update the model from the event source >> from the master. That should be fairly easy to achieve by wrapping the >> Program with one that does this. >> >> For a multi-user application, a simple but perhaps too inefficient way of >> keeping things in sync would be for all user events to be round-tripped >> through a message queue in order to put them in a sequential order that is >> the same for all participants. So local input events would not go straight >> to the update function, but be round tripped over the network. Would >> probably work well enough for a small number of users on the LAN. >> >> Just curious to know if anyone has ever experimented with Elm along these >> lines. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Elm Discuss" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Zach Kessin > Skype: zachkessin > > -- > You received this message because you are subscribed to the Google Groups > "Elm Discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
