Re: workspace stuff (was: Re: move/copy/delete/etc in a change set)

From: Greg Stein (gstein@lyra.org)
Date: Fri, Aug 11 2000

  • Next message: Internet-Drafts@ietf.org: "I-D ACTION:draft-ietf-deltav-versioning-07.txt"

    Date: Fri, 11 Aug 2000 00:13:14 -0700
    From: Greg Stein <gstein@lyra.org>
    To: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
    Cc: ietf-dav-versioning@w3.org
    Message-ID: <20000811001314.N19525@lyra.org>
    Subject: Re: workspace stuff (was: Re: move/copy/delete/etc in a change set)
    
    On Thu, Aug 10, 2000 at 11:44:50PM -0400, Geoffrey M. Clemm wrote:
    >    From: Greg Stein <gstein@lyra.org>
    >...
    >    [ for the record, I want multiple checkouts, but only for short periods of
    >      time -- the client will do MKACTIVITY, CHECKOUT, MERGE <activity>; if a
    >      couple clients are hitting the server at the same time, there is a point
    >      between CHECKOUT and MERGE where they could both have it out at the same
    >      time; I want this allowed in case the first client aborts before the final
    >      MERGE step; I don't want the second guy prematurely locked out ]
    > 
    > Sounds reasonable.  Although those "short periods of time" can end up being
    > rather long ... (:-).
    
    hehe. You bet! Which is why (IMO) multiple checkouts can be a Good
    Thing(tm). If somebody had to wait for an administrative action before being
    able to check something out, then you'd have some peeved engineers :-)
    
    >...
    >    Euh. Nope. Section 11.1 is the issue I'm referring to. It states that any
    >    request with a Workspace header must fail if there is a corresponding
    >    internal member.
    > 
    > Wait, wait!!  That clause was supposed to be deleted.  We decided to
    > kill it because of the reasons you describe below.  No wonder you
    > don't like workspaces!
    
    Ah! Okay. I take back what I said :-)
    
    Can I move on and dis baselines then? :-)
    
    >...
    > Well, I'm glad you raised the issue, since this is a bug, not a feature.
    > In general, if something you see doesn't look right, please raise it as
    > an issue (especially if you're going to be doing any implementing!).
    > Even if it is there for a good reason, if that reason is not clear from
    > the spec, that's a bug that should be fixed by improving the explanation.
    
    Okee dokee. Baselines aren't clear as to "why". I'll read the latest spec to
    see if there is more info there, and then try to articulate some specifics.
    But that probably won't happen for a little while (since I'm not going to
    need them for Subversion). And you're leaving for a break... IOW, it appears
    it'll wait a couple weeks.
    
    Thanx,
    -g
    
    -- 
    Greg Stein, http://www.lyra.org/