On 08/23/2016 12:07 PM, Per Jessen wrote:
To me, Daniel's clearly accessing the webserver using fish:// from dolphin. If he was editing directly on the webserver, the issue would not exist.
To me, you are being ambiguous. "Editing directly on the webSERVER" That could mean the program or the machine. Accessing the file directly, be it from the same machine just like a regular file on a file ssytem or a NFS mount is one thing. As far as I can make out, FISH means that the file is TRANSFERRED, that is a copy is made and downloaded to the client machine. it is edited, as a copy, on the client machine. Now you may say that even on a regular file system the editor works with a copy, which is written back on file close, and that's true. The assumption that Daniel is making is that there is a temporary copy transferred (aka downloaded, which web servers are wont to do), a temporary copy of the temporary copy is edited, the temporary copy of the temporary copy is written to the temporary copy and finally the temporary copy is coped back by the FISH protocol and the web server accepts it. A number of things about this occur to me. a) I'm not sure that FISH copies back. Does it? b) I can't see a regular simply accepting an upload in a eciprocal fashion to the download. c) Shouldn't he be using some WebDAV type of thing to support the upload. I mention (c) because I DO maintain files in a similar manner with my openCloud server. Either way, I'd like to see the server logs surrounding the transaction. I'm sure they can be isolated. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org