Re: Some questions...

At 10:22 PM +0100 7/16/03, Tony Hoyle wrote:
>Remember I'm not trying to make an SV client talk to a CVS server
>(that'd probably be impractical) but the other way around - you can
>dump a lot of junk at the CVS client and it'll faithfully send it
>back during an update/commit without looking too hard at it. It's
>not a direct 1:1 translation, and I doubt it's a small project (I
>reckon a couple of months to get it usable) but it's worth doing.

I guess your idea here is: a process (or COM server, perhaps, some
entity), running on the client machine

* that receives the CVS protocol messages
* intuits the underlying meaning
* performs the corresponding svn operations
* including whatever annotations, expansions, or ellipses might be
necessary because of the differences
* receives the SVN responses
* intuits their underlying meaning
* expresses that as responses to the CVS protocols

So, for example, CVS update consists of the client sending a list of
what it has, whereas SVN update consists of the client sending what
it needs (unless I got that backwards, but either way the example
works). The one list is essentially the complement of the other. So
this intermediary would intuit "update," respond "yeah, yeah, yeah"
endlessly, meanwhile launching an SVN update (and the standard SVN
code would send along the list of what's needed).

-- 
-==-
Jack Repenning
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
o: 650.228.2562
c: 408.835-8090
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org