PDME 1.0b2 NO IDEA Avatar
  1. OMG Issue

PDME — PDM Enablers file locking behavior

  • Key: PDME-131
  • Legacy Issue Number: 2485
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The PDM Enablers convenience document mfg/98-02-02, section 2.6.1,
    "PdmDocumentManagement Overview," explains checkin/checkout as follows:

    To perform a checkout, the client would first lock the file using the
    lock() operation. The client then transfers the file"s contents from
    the PDM server to it"s file system. To perform a checkin, the client
    creates a new DocumentIteration. It then creates a new File,
    associates it with the DocumentIteration, transfers the contents of the
    file from the client to the PDM server. Lastly, it unlocks the file.

    If every checkin creates a new DocumentIteration, then it follows that I
    would never actually change a File once it has been uploaded, because that
    would be an untracked change, and untracked changes are always bad and
    evil. So I don"t know why I"d ever need to lock a File.

  • Reported: PDME 1.0b1 — Mon, 22 Feb 1999 05:00 GMT
  • Disposition: Resolved — PDME 1.0b2
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT