if the connection is lost then the program on the remote end won't get a "final save" operation and the original file will be unchanged while the transient file with the incremental changes up to the lost connection can be saved like many editors do (emacs saves this as '#{filename}#'). on the local client side it should save the file locally if it did not get a proper response to "final save" before either a timeout or connection loss. this design should also look on the local host for file recovery.
i don't know how RPC can work over the existing SSH connection (which may be relayed over things like Tor so making a separate connection is not an option).
i don't know how RPC can work over the existing SSH connection (which may be relayed over things like Tor so making a separate connection is not an option).
Tradition is peer pressure from dead people
What do you call someone who speaks three languages? Trilingual. Two languages? Bilingual. One language? American.
What do you call someone who speaks three languages? Trilingual. Two languages? Bilingual. One language? American.