kfogel@collab.net wrote:
>"Peter N. Lundblad" <peter@famlundblad.se> writes:
>
>
>>I know you and others have been discussing blame caching on the server. I
>>would say this is the usual tradeoff between API flexibility and speed:-)
>>The problem with server support is that we hardcode the diffing algorithm,
>>or at least removes the possibility to have other diff programs provide
>>the blame information. We're not doing this today, but I don't like to
>>move this to the server if we can avoid it. Also, we should consider other
>>queries that are similar to blame, such as functionality to ask "who
>>deleted this line"? (I've actually seen this requironment somewhere.) The
>>problem with moving specialized functions to the server is that they have
>>to be supported by all three (though one is trivial) access methods.
>>
>>
>
>Throughout this thread, there has been a fundamental misconception
>about how to implement blame caches on the server-side. I will now
>grace you all with a revelation about the One True Way to do it.
>
>/me pauses to preen himself
>
>Okay, am I annoying enough yet?
>
>
Quite, but I'll note that your proposal has the singular benefit of
already being implemented. Vdelta is nothing but a set of binary
difference ranges. :-)
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Nov 20 18:59:58 2004