I think what you are talking about is classical event sourcing or a variation of it. Each new piece of data is a new event persisted somewhere (e.g., file) on the local system. Then when remote system comes online the event source stored up until this point would have to be replayed for the remote system, thus preserving the over-time state of the event stream allowing access to both current state as well as point-in-time. Is that what you trying to accomplish or your pieces of data are completely independent from one another (no historically significant timeline)?
Cheers Oleg On Mon, Feb 10, 2014 at 4:54 AM, joseph <[email protected]> wrote: > Hi Roland > > Thanks a lot for your answer. > > The end target would be to have the data on the local system and allowing > creation of new data while offline. Then, on being online again, the diff > would be pushed and resolved. I had played with akka-persistence regarding > this application and I was wondering how I would implement such an use case > with it. > > Thanks again > > best > > > > > On Monday, February 10, 2014 8:03:32 AM UTC+1, rkuhn wrote: > >> Hi Joseph, >> >> what exactly do you want to achieve? I'm asking because Akka itself does >> not really have any end-user features, it is only a library for building >> your own functionality. The precise meaning of master/master or >> "disconnected mode" depends very much on what you are building with Akka, >> not on Akka itself. >> >> Regards, >> >> Roland >> >> 9 feb 2014 kl. 21:57 skrev joseph <[email protected]>: >> >> Hi >> >> While working on the train the other day I realized how much I missed git >> disconnected capacities. >> >> Ever since, this has stuck into my mind and I'm thinking about how to >> implement such mechanism. >> >> I looked around regarding akka but apparently master/master and >> disconnected stuff aren't too much spoken of. Did I miss something obvious >> ? Are they some best practices around or, even better, examples ? >> >> Thanks in advance >> joseph >> >> -- >> >>>>>>>>>> Read the docs: http://akka.io/docs/ >> >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user >> --- >> You received this message because you are subscribed to the Google Groups >> "Akka User List" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> >> Visit this group at http://groups.google.com/group/akka-user. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >> >> *Dr. Roland Kuhn* >> *Akka Tech Lead* >> Typesafe <http://typesafe.com/> - Reactive apps on the JVM. >> twitter: @rolandkuhn >> <http://twitter.com/#!/rolandkuhn> >> >> -- > >>>>>>>>>> Read the docs: http://akka.io/docs/ > >>>>>>>>>> Check the FAQ: http://akka.io/faq/ > >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user > --- > You received this message because you are subscribed to the Google Groups > "Akka User List" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/akka-user. > For more options, visit https://groups.google.com/groups/opt_out. > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/groups/opt_out.
