[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[RFC] Added editor driver restrictions

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2003-10-22 16:55:48 CEST

On and off IRC, there's been alot of talk about trying to speed up
checkouts. Part of the cost we are paying on checkouts and exports is
that anytime there is keyword substitution or EOL translation to be
done, we do so like this (give or take a rename or so):

   - first write a pristine copy of the file (text-base).
   - re-read the text-base, translating/substituting into the working file.
   - for exports, we then remove the pristine version.

It occured to me (and Karl, and perhaps others) that we could perhaps
speed this up if we knew before getting the file contents that we were
going to have to do translation. If we did, exports could be reduced
to:

   - if translating, do so on downloaded data stream (on-the-fly).
     else, just dump the stream to disk.

But for checkouts, we still need *both* the translated and
untranslated versions. So, I considered the creation of
svn_stream_tee(), which splits an incoming stream into two streams.
Using this mechanism, we could make checkouts:

   - setup a stream tee, routing output-1 to the text-base, and
     output-2 to the working file.
   - if translating, do so to the output-2 stream on-the-fly.

I'd be willing to test this out to see if it works out as well as I
hope. But I wanna make sure no one objects to the added restriction
this would add to the editor interface. If we can't bank on having
the properties before the file contents, the rest of this proposal is
worthless.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 22 16:57:20 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.