Currently, Sahara Sync's default client does not handle the case where the host daemon is not available very gracefully. If using streaming changes, the connection used to receive changes will be dropped without being reestablished, and any blob changes will be silently ignored.
hoelzro
commented
12 years ago
Currently, Sahara Sync's default client does not handle the case where the host daemon is not available very gracefully. If using streaming changes, the connection used to receive changes will be dropped without being reestablished, and any blob changes will be silently ignored.