RE: Enumerating repositories and worksp

From: Tim Ellison OTT (Tim_Ellison@oti.com)
Date: Wed, Feb 23 2000

  • Next message: Vasta, John: "RE: Enumerating repositories and worksp"

    From: Tim_Ellison@oti.com (Tim Ellison OTT)
    To: jvasta@rational.com (Vasta, John)
    Cc: ietf-dav-versioning@w3.org ('Delta V')
    Message-ID: <2000Feb23.132535.1250.1486114@otismtp.ott.oti.com>
    Date: Wed, 23 Feb 2000 13:26:31 -0500
    Subject: RE: Enumerating repositories and worksp
    
    
    <john>
       I think you can have it both ways, if there was
       a way to discover whether a server has constraints
       or not. The spec is almost there; we just need a way
       to discover whether the server has repositories, and
       where it insists workspaces be located. If there were
       two properties defined somewhere (e.g.
       DAV:repositories-root and DAV:workspaces-root), then
       if either of those properties are defined, a client uses
       their values to form URLs to repositories (and therefore
       activities, configurations, and versioned resources) or
       workspaces respectively. If a property is not defined,
       then clients are free to use any URL they please, for the
       corresponding type of resource.
    </john>
    
    If you were to follow this method, then I suspect that you would put 
    DAV:workspaces-root on repositories too wouldn't you?
    
    Then the problem becomes finding repositories--and if I understand, you 
    suggest that a list is available at a well-known location (e.g., any 
    resource, "/", etc.)
    
    Tim