1. OMG Issue

FTAM — How does transfer operation determine FileTransferSession object identity

  • Key: FTAM-14
  • Legacy Issue Number: 4183
  • Status: closed  
  • Source: DSTC ( Ted McFadden)
  • Summary:

    From the description in Chapter 3, it is not clear how the
    FileTransferSession::transfer method is actually accomplished.

    Chapter 4 Section 4.5.1 describes the FileTransferSession examining
    the File reference's attributes to determine whether it is to initiate
    the transfer or receive the file. The initiator
    FileTransferSession::transfer implementation must then call transfer
    again on the target FileTransferSession.

    How, in a portable fashion, is a FileTransferSession to determine if
    it is the same FileTransferSession referred to in the src or dest File
    associated_session attribute?

    1. _is_equivalent cannot be used to compare FileTransferSession or other object
    references as a false return is inconclusive.
    2. There are no object identity operations defined on the
    FileTransferSession interface.
    3. None of the other File attributes denote unique identity (name,complete_name,
    as the src and destination file names can be identical.)

    Requested Action: Clarify how the File's attributes allow a FileTransferSession
    implementation to determine File ownership.

  • Reported: FTAM 1.0b1 — Tue, 30 Jan 2001 05:00 GMT
  • Disposition: Resolved — FTAM 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 21:48 GMT