I'm using MobileMe to sync and still have all these issues. Why doesn't OF use the normal OS X sync services in the first place? Then I think there would be none of these issues.
These forums are now read-only. Please visit our new forums to participate in discussion. A new account will be required to post in the new forums. For more info on the switch, see this post. Thank you!
|
|
FAQ | Members List | Calendar | Today's Posts | Search |
What should I do about "Client has not been synced" warnings? [Fixed: see thread] | Thread Tools | Search this Thread | Display Modes |
Member
2010-06-17, 04:23 AM
I'm using MobileMe to sync and still have all these issues. Why doesn't OF use the normal OS X sync services in the first place? Then I think there would be none of these issues.
Post 41
|
Member
2010-06-17, 10:53 AM
It struck me later that you're probably designing for the use case where the client is gone and really isn't coming back. In that case, perhaps a banner at the top of the OmniFocus window would be better than a modal dialog. I'm thinking of something like what you see at the top of http://stackoverflow.com when there are new messages for you. It could sit there until you dismiss it or act on it. The problem with a modal is that it interrupts my flow and makes me feel like I must do something about it now.
Post 42
|
Member
2010-07-09, 01:11 PM
Quote:
Quote:
I've spent a bit of time ignoring one of my devices while intensively using the others recently, and my experience is that if you do this, as some seem determined to do, it essentially guarantees that you will not only slow down the devices you use frequently, but also when you do finally go to use the neglected device, it will cause a big database compaction to occur (all the devices finally being on the same page), and you'll have to twiddle your thumbs while the newly compacted database is written back to the server, possibly over a very slow cellular connection. Maybe I just don't understand a workflow where it's more important to have a rather stale copy of your data ready and waiting to be used immediately (but rarely) than having speedy results on the usual case.
Post 43
|
Member
2010-07-09, 11:42 PM
Again, whpalmer, you fail to understand my concern. I paid for this software (and the iPhone app, and the inevitable iPad app, when it arrives) so that I can put my data into it in substantial part so that I do not forget it. Throwing away any part of my data without giving me any recourse to avoid the operation completely defeats that purpose and undermines the apparent utility of the entire software family for me. Giving me the "option" to manually re-enter my data again after I had already entered it once makes me question why I expended the effort of putting the data into the software in the first place if it's going to be at risk of arbitrary discard. Why did I bother spending the time to enter that data in the first place if I'm always going to be at risk of having to manually reconcile it again? There haven't even been any details provided here of how reconciling such an event would work in the first place, which leaves me even more concerned.
Given all of this, I've already suggested that as an alternative to reverting this behavior, how about providing an opt-out for the people who understand the implications and understand that letting the databases drift too far out-of-sync will have performance implications? That way you can satisfy those who don't understand why their syncs are getting slower but not scare off those who take data integrity very seriously.
Post 44
|
Member
2010-09-10, 08:09 AM
I see the new release has dropped: so is there any way to turn this behavior off?
Post 45
|
Quote:
Code:
defaults write com.omnigroup.OmniFocus SyncClientDeadAge -float 7862400 The best-of-both-worlds way I'd like to solve stale clients going forward is to make it easy to merge and synchronize databases from unregistered clients, so we can merge changes from them without having to keep tracking every change which has happened while they were unsynchronized. (That would also be useful for initial synchronizations as well, such as when someone first sets up their iPhone and iPad independently and later decides they'd like to sync them together.)
Post 46
|
Member
2010-09-12, 11:26 AM
I'm assuming that this mechanism is not in the mobile clients, then? (Since there's no way to do a defaults write on those platforms it would be a problem if it was...)
Oh and is there a limit on this interval? Could I set it to something like 30 years if I wanted to?
Post 47
|
Quote:
Quote:
Post 48
|
Member
2010-10-05, 10:04 PM
When did this go into the mobile clients? I've already had two clients get dropped before I upgraded anything on the desktop systems to 1.8. Not happy. :mad::mad::mad:
Post 49
|
Member
2010-10-06, 04:16 AM
Did you set the dead client timeout as Ken instructed?
Post 50
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
"Email-to-OmniFocus" entry in client list? [A: created by Sync Server's Mail Drop feature.] | Robejazz | OmniFocus 1 for Mac | 1 | 2013-03-11 04:03 PM |
Sync adds "Process" prefix to Perspectives [A: Bug, will be fixed in update. Sorry!] | b-dr | OmniFocus for iPhone | 3 | 2012-09-24 12:56 PM |
"Jump to specific canvas" action wrong in exported PDF? [A: Bug, fixed in 5.4.1] | Georgy | OmniGraffle General | 4 | 2012-07-31 03:44 PM |
Some synced events not appearing in iCal [A: check "add blocked items" in OF Prefs.] | peterlemer | OmniFocus 1 for Mac | 2 | 2012-02-08 09:06 AM |
"Existing sync client entries will eventually go stale"?? | al_f | OmniFocus Syncing | 2 | 2008-09-12 02:11 PM |