Re: [MLO] MLO's cloud sync management of conflicting data

2012-10-28 Thread Marc García Martí
I said I'm no software developer, but if the app itself checked current clock locally before uploading content, it could attach the current time to the information. That way, assuming all the devices have a valid and reliable time, the cloud itself could figure things out automatically. Thanks

Re: [MLO] MLO's cloud sync management of conflicting data

2012-10-28 Thread Trish Putnam
The problem would be with guaranteeing that all clocks had a valid and reliable time to a very high degree of accuracy. One thing that could be done, perhaps, is to provide a setting to allow the user to decide whether to trust timestamps. If yes, then the computer handles conflict resolution

RE: [MLO] MLO's cloud sync management of conflicting data

2012-10-28 Thread mlo
Hi Trish and Marc. I will admit that I have done coding in my life. This clock issue has been solved. It’s not necessary that any of the clocks in the system be set correctly, only that none of them are gaining or losing time quickly enough to be noticeable. What happens is that whenever a client

RE: [MLO] MLO's cloud sync management of conflicting data

2012-10-28 Thread mlo
Hi, Marc. There are a number of scenarios in which relying on the latest timestamp does not work. Three that come quickly to mind are (1) Today’s changes to yesterday’s task, (2) you are both right, and (3) trickle down. Today’s changes to yesterday’s task I have a task that repeats daily.

Re: [MLO] MLO's cloud sync management of conflicting data

2012-10-28 Thread Trish Putnam
Basing the timestamp on the time of transmission requires reliance on the false assumption that all devices making the change are online and transmitting all the time. For example: I'm on a plane with my phone and my tablet. Both are properly offline for the flight. I make a change to my data

Re: [MLO] MLO's cloud sync management of conflicting data

2012-10-28 Thread Dwight Arthur
I may have been unclear, I am not proposing that latest transmission time wins. I agree with you that transmission time alone would give bad results. Specifically I am proposing an adjusted timestamp which is {client's local time of edit} minus {client's local time of transmission} plus

Re: [MLO] MLO's cloud sync management of conflicting data

2012-10-28 Thread Dwight Arthur
/note: I submitted this by email and it went out to the list be email but did not appear on the server. So I am posting it directly to the server. If you are seeing this email for the second time my sincere apologies and please do not waste your time reading it again./ Hi, Marc. There are a

RE: [MLO] MLO's cloud sync management of conflicting data

2012-10-18 Thread Marc García Martí
: dijous, 18 / octubre / 2012 04:56 Per a: mylifeorganized@googlegroups.com Tema: RE: [MLO] MLO's cloud sync management of conflicting data Hi, Kitus. As you mention, it would be great if sync conflicts could be figured out and resolved by the software. I guess the issue would be, how far

[MLO] MLO's cloud sync management of conflicting data

2012-10-17 Thread kitus
Hello, I was wondering, can't the cloudsync handle conflicting data autonomously? why do I have to be prompted when the same action has been updated from different devices? I really don't like having to step off my train of thoughts and think whether A or B is correct. I really think that

RE: [MLO] MLO's cloud sync management of conflicting data

2012-10-17 Thread mlo
other tools that do it - which ones do you think get it really right?? -Dwight From: mylifeorganized@googlegroups.com [mailto:mylifeorganized@googlegroups.com] On Behalf Of kitus Sent: Wednesday, October 17, 2012 10:54 AM To: mylifeorganized@googlegroups.com Subject: [MLO] MLO's cloud sync