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

Re: Issue #3255: client capabilities in start-commit

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Thu, 07 Aug 2008 13:19:34 -0400

david.x.grierson_at_jpmorgan.com wrote:
> Hi Joe,
> I've just confirmed this on RHEL4 + 1.5.0
> With KeepAlive off this defect manifests itself.
> With KeepAlive on the mergeinfo is reported in the client capabilities.
> I'll update the defect appropriately.

What options do we have for resolving this? It would seem (to me, who
hasn't been following this thread much) that we need one of two things:

    - a way to persist the client capabilities through the lifetime of the
      high-level Subversion operation (the commit). But that's sorta
      contrary to the whole way our stateless protocol works, isn't it?

    - the client to transmit capabilities in the same request which makes
      use of them (which is ... MKACTIVITY?). But is that a fair demand?

C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on 2008-08-07 19:19:50 CEST

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.