Because there is no standard error code to tell clients that the error was due to a web proxy.Ĭlients can fail for various reasons not only web proxy.īut in this case the failure is being falsely reported as “Synced”, instead of “Failed”? This is individual use - for example, my home workstation has Inkdrop installed, as does my laptop which I take to different locations, some proxied. No, since it is designed to be basically used by a person, not a team. The local revision is present, but is sometimes several entries deep from the previous revision, so it looks like I’ve missed it during previous sync issues.Īdditionally, after further sync attempts on and off the proxy from the client, it generated a entry for the note which is great.Īpologies! Also, the patch view is very cool. I mean, if you make a change on client A, the change is only retained in the revision history on client A.Įdit - to confirm, on testing again this is working as you have described. When a normal connection is restored, data is lost from one update.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |