1. OMG Issue

FTAM — The Directory::list operation is underspecified

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

    The parameters of the Directory::list method are underspecified which
    makes interoperability a problem. (We just went through this with the
    NamingContext::list operation in the Naming RTF/FTF.)

    A more rigorous definition of list (borrowed from Section 3.3.8 of
    the INS spec formal/00-08-07) is:

    void list (in unsigned long how_many,
    out FileList fl,
    out FileIterator fi);

    list returns the Files contained in a Directory in the parameter fl.
    The fl parameter is a sequence where each element is a FileWrapper.

    The how_many parameter determines the maximum number of Files to return
    in the parameter fl, with any remaining bindings to be accessed
    through the returned FileIterator fi.

    • A non-zero value of how_many guarantees that fl contains at most
      how_many elements. The implementation is free to return fewer than the
      number of Files requested by how_many. However, for a non-zero
      value of how_many, it may not return a fl sequence with zero elements
      unless the Directory contains no Files.
    • If how_many is set to zero, the client is requesting to use only the
      FileIterator fi to access the Files and list returns a zero
      length sequence in fl.
    • The parameter fi returns a reference to an iterator object.
    • If the fi parameter returns a non-nil reference, this indicates that
      the call to list may not have returned all of the bindings in the
      Directory and that the remaining Files (if any) must be retrieved
      using the iterator. This applies for all values of how_many.
    • If the fi parameter returns a nil reference, this indicates that the
      fl parameter contains all of the Files in the Directory. This applies
      for all values of how_many.

    Action Requested: Make description of list operation cover these
    interoperability points.

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

    see above

  • Updated: Sat, 7 Mar 2015 04:32 GMT