-- Eric wrote:
> The best bet (and the solution I settled on) was to have the client do
the
> task, and then let the server check the results and optionally abort
if
> they are not correct. This solves the "client not doing the right
thing"
> problem.
There seem to be a few issues with this approach:
- The end user must initiate this client side task
- The client side task must obtain formatting information (style) from
the
server (either through svn or shared network resource) and could be
outdated
- The pre-commit trigger to verify the client did the right thing ends
up
duplicating all the work the client just did (potential performance
issue)
- If the client did the wrong thing, this failure must be made visible
to
the end user, and that user must then initiate a client side task to
fix it
Another approach I have considered is to do reformatting as a
post-commit
action which might initiate and commit a new transaction with formatting
fixes. This approach still has some drawbacks, though. I wonder if
anyone
has tried this.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 15 02:25:50 2004