Branko Čibej <br...@wandisco.com> writes: > For a start, this would require a major change in the wire protocol, > where the server would, as a response to a successful commit, report any > additional "magic" changes to the client. The problem with this is that > it is error prone; the response may never arrive, for any number of > reasons. Therefore, the client could not mark commtited items up-to-date > until and unless it received the response. Since at least the DAV > protocol is stateless, this implies all sorts of complications and the > introduction of intermediate states in the working copy. > > In short: yes, it'd be hard.
Another problem: what does the client do when it receives the changes? The client would update the pristine text/properties to match the repository, but what about the working text/properties? After a commit should the working copy match the repository or not? Suppose the user commits a text change and the server replies with a file delete, what happens to the working file? Does the user lose the data? Does the commit produce some sort of conflict? -- Philip Martin | Subversion Committer WANdisco // *Non-Stop Data*
