Jack Repenning wrote:
>>From: Branko Cibej [mailto:brane@xbc.nu]
>>
>>There's a policy involved here. It says that the server shall
>>never, ever try to second-guess the client, and it will not
>>change the contents of the files in any way. The server's one
>>and only job is to store and retreive data.
>>
>>
>
>Elsewhere in this discussion, there seems also to be a policy implied or
>recommended, that the client "shall never, ever ..." as well. Together,
>these amount to a policy that SVN "shall never, ever ...."
>
Heh. :-) Yes, we do have such a "never, ever" policy for the client,
too, but it's not exactly the same as for the server. So the union of
the "never, ever"'s isn't isomorphic to the members sets.
>If that's where we're at, it would seem to eliminate many of these
>requested features a priori.
>
It does. We /a priori/ reject features that require the server to modify
the data it receives from the client.
>It would certainly shorten the discussions a lot, anyway ;-)
>
>
Indeed, but this particular feature doesn't require the server to do
anything. As for client-side scripts -- well, I agree in spirit with
those people who are against them.
But I believe there might be a safe solution: Integrate a scripting
language -- say, Python -- into the client, make sure that all clients
use the exact same version of that language, and store the scripts
themselves on the server. That way all clients will always use the same
scripts, and interpret them in the same way.
--
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 27 00:27:54 2003