Post a Comment
Gears have been deprecated by google and is no longer working, I guess they are trying to integrate with html5 local storage.
However the fix is to manually signout the google account and clear the cookie (apparently clearing the cookies is not enough) and sign in with one account at a time only.
I've experienced this bug, but it does not lock you out of your documents. It only happens when you are logged in with multiple accounts and even then under certain conditions. It's an inconvenience but not a disaster.
Of course there are disadvantages to using the cloud to store your documents, but I don't think uptime is one of them. If you store your documents locally you could also loose access to them temporarily. Local documents can even get lost completely, something I think is quite unlikely to happen on Google docs.
But if they are stored in the cloud, but only cached on your system, that is the best option. That way, if you can't access the net, or the service provider has a problem, you still have your documents on your system. Or if you hard disk goes kaput, you still have all the documents in the cloud.
Read the message above. You only lose access in certain situations. And then its easy enough to restore access by logging out of your other sessions. But you are right in that if people were locked out long term, I would call that an outage. As is, its just an inconvenience.
Quite the workaround I suppose!
Yes, and that's certainly better than the alternative. Although it's still a pain when trying to work on a collaborative document... if one person leaves the window open when they go home, nobody else can touch it when they call in sick the following day. Better support for concurrent changes (or near-concurrent) would be nice...



