On Friday, May 31, 2002, at 11:55 AM, Karl Fogel wrote:
> Colin Putney <cputney@whistler.net> writes:
>> 2) Decree that log messages must be text, and store the metadata
>> specifiying the character set. Have the clients pass the character set
>> to the core libraries and have the libraries return the character set
>> along with the log messages at retrieval time.
>
> I like (2), but it doesn't even have to decree that they be "text".
> If we're storing another property saying what the charset is (or what
> Subversion's best guess is, anyway), then we just store the exact
> sequence of bits the user specified for the log message, along with
> metadata saying how to interpret that sequence of bits.
I'd call this option 3. The difference is small in terms of
implementation details, but large semantically. If you just store bits
you'd have to store a mime-type as well as an encoding, and (correct)
clients have to be prepared to deal with non-text log messages. So the
trade off between (2) and (3) is greater flexibility for log message
(Word or RTF documents might be useful for example) vs higher barrier to
entry for client implementors.
Colin Putney
Whistler.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jun 1 14:10:49 2002