"DeltaV, which has been ripped out..."

[Steve Simon <st...@quintile.net>]

> That was our use of DeltaV, which has been ripped out in 1.7. (well...
> newer hotness, and some back-compat remaining)

Hi,

I was a little purturbed to read this, are there any references to
what is being dropped and what is kept?

I a have written a WebDav client, mainly as an SVN client, and am
just girding my loins ready to embark on DeltaV support so I can
checkin new code.

Is this code going to be obsolete before it is finished?

Also, how will this effect thrid party clients such as Tortoise
and Smart SVN clients?

-Steve

Re: "DeltaV, which has been ripped out..."

[Mark Phippard <ma...@gmail.com>]

On Tue, Apr 6, 2010 at 6:37 AM, Steve Simon <st...@quintile.net> wrote:
>> That was our use of DeltaV, which has been ripped out in 1.7. (well...
>> newer hotness, and some back-compat remaining)
>
> Hi,
>
> I was a little purturbed to read this, are there any references to
> what is being dropped and what is kept?

Nothing was droppd.  The SVN client is just going to have a more
efficient conversation with the server via HTTP when both client and
server are running 1.7.

> I a have written a WebDav client, mainly as an SVN client, and am
> just girding my loins ready to embark on DeltaV support so I can
> checkin new code.
>
> Is this code going to be obsolete before it is finished?

It sounds like it was obsolete before you started :)  But seriously,
nothing has really changed.  You can still do this.  Note that SVN has
never truly supported DeltaV though, so a generic DeltaV SVN client
may or may not work.

> Also, how will this effect thrid party clients such as Tortoise
> and Smart SVN clients?

TortoiseSVN uses the SVN client libraries.  So it will just have a
more efficient client/server communication.  SmartSVN uses SVNKit, so
it will depend on when they choose to adopt the simpler protocol.  It
is not like pre-1.7 clients are going to stop working though.  All of
the old protocol is still there and supported.


-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/