Well, I just ran into my first hurdle: the current svnserve protocol demands that capabilities in the standard capabilities string list be of the protocol data class "word", which is limited to strings with letters, numbers, and hyphens only. I think that pretty much rules out having this functionality "just work" for existing servers in the wild -- admins would need 1.8+ servers.
But if we need a new server + protocol changes to accomplish this anyway,
then what changes to make?
1. change the definition of "word" to include more characters? Feels
wrong. -1
2. introduce a new protocol data type that covers the character classes we
need, and change the protocol to expect that primitive type instead of
"word" for capabilities? Hrm... feels like smashing a fly with a
Buick. -0
3. just use the "string" type for capabilities, but with server-enforced
additional formatting constraints. +0/1? (But is this meaningfully
different from suggestion #2?)
4. something else?
--
C. Michael Pilato <cmpil...@collab.net>
CollabNet <> www.collab.net <> Enterprise Cloud Development
signature.asc
Description: OpenPGP digital signature
