Ying Dong, MG et al, there are some difficult design tradeoffs in creating an automatic synch between devices that have an intermittent connection. I think if you work out how you would like these tradeoffs resolved, and the people following this request agree, you might make it easier and perhaps more likely for the developers to try to build it.
The big issue is, when synch fails to lack of connectivity, do you tell anyone? This is a bigger issue with wifi than cloud. With cloud, if there's a collectivity issue, it most likely means that my device has lost its internet connection. Second most likely, the cloud server is down. Here's the thing: if your phone has lost connectivity you will most certainly notice without MLO having to tell you. And if the server is down MLO people will get alarms. So the problem will be fixed and it's not up to MLO. Wifi sync only works if both devices are present and connected at the same time; if there's an issue with that MLO is very possibly the only one who cares, so it's up to MLO to take action to get it resolved. Consider this: A busy executive has a hard day at work, completing many tasks and marking them done on her work desktop, as well as scheduling new tasks. End of the day, on the train home she goes to review todays overdue tasks and plan for tomorrow and she discovers that she has yesterday's data, there were no syncs today. Maybe this morning her phone got a new IP address from DHCP and all day the desktop was trying to send updates to the old address. This is clearly unacceptable so we add an alarm when sync fails. Our exec leaves work, goes to the train, no more connectivity to work LAN. Every 5 minutes (or so) the phone tries to sync and fails. Which means every 5 minutes or so the alarm goes off. Very, very annoying. So we change it: alarm if no sync once every 8 hours. All is fine until 3am when the phone beside the bed wakes everybody up because there has been no sync. How should this be handled? Another issue: today each device knows who to sync with because the user types in all the IP addresses. Nick has already mentioned the difficulties with this issue. So if IP addresses change (relocation, DHCP, etc) does the user have to notice and type it in before MLO will resume sync? Or will MLO crawl the LAN looking for other MLO instances with which to sync? What happens if the LAN has a few different people each using their own copy of MLO? On Saturday, June 15, 2019 at 3:41:14 PM UTC-4, imajeff wrote: > > You need those checks if it's not automatic. Trust me I'm a software > engineer. If server connection is not available, don't sync. > > Cloud sync is not as simple as you think. That's why it costs more to keep > it working > > On Sat, Jun 15, 2019, 09:11 Nick Clark <[email protected] <javascript:>> > wrote: > >> As you suggest it is not as simple as just adding a timer to initiate the >> sync. The mobile device would need to check if there is a network >> connection to a PC with MLO installed. What if the PC or mistaking device >> had a different IP address to the last time it connected, a likely >> situation if used on a corporate network using DHCP for address allocation? >> What if more than one instance of a PC with MLO installed is found - which >> to use? >> >> By contrast the cloud sync is simple - if there is an internet connection >> it can sync. >> >> -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" 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 https://groups.google.com/group/mylifeorganized. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/02073ba2-1696-4a5a-b656-af7e371342bb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
