Mark Phippard wrote:
> I find this post confusing because I assume its intent is to disagree with
> me, but I feel like what you actually wrote is in support of my proposal.
No worries, there was no general intent of disagreement. I just wanted
to express that we're walking a thin line here.
> I believe the validation should be part of the UI for precisely the
> reasons you state. It provides the best user experience, and allows an
> administrator to get around it when necessary by using the command line
> client.
IMHO the goal is to provide both a good user experience and a safe
integration which could _not_ easily be worked around (otherwise users
work around it because they simply don't like the idea, are too lazy,
you name it).
This could be achieved through:
1. validation on the server side (client-independent!)
2. support for entering valid information on the client side
3. (optional) pre-validation on the client side, if you feel that even
with (2) in place the chance for the pre-commit hook throwing an error
is too high.
Re administrators: if necessary they can still work around the server
side validation by either temporarily disabling the hooks (they'd have
to disallow other connects in the meantime) or implementing some magic
in the hooks which identifies administrator actions. (No specific idea
though on how I'd do that...)
Hopefully less confused/confusing this time...
Lars.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Oct 27 18:27:42 2004