Issue 4427:  ftam-ftp FTF issue: Exception definitions                                                                                                                                                              (ftamftp-ftf)
Source: DSTC (Mr. Ted McFadden, mcfadden@dstc.edu.au)
Nature: Uncategorized Issue
Severity: 
Summary: The spec defines six exceptions that carry no information other than a
text string to describe the error. This leads to cumbersome coding on
the client side.

Consider a single exception with a reason code. This conveys the same
information without requiring 5 or 6 catch blocks in some languages.
Resolution: see above
Revised Text: Section 3.1.1 Exceptions
Actions taken:
July 25, 2001: received issue
Discussion: 
Resolution
Exception types changed to FileSystemError with an ErrorCode and TransferError which
is like a FileSystemError but can identify whether the problem is at the source or sink end
of the connection. The ErrorCodes are defined as const values to allow for future addi-tions.
End of Annotations:=====
Date: Wed, 25 Jul 2001 15:06:03 +1000
From: Ted McFadden <mcfadden@dstc.edu.au>
To: issues@omg.org
Subject: ftam-ftp FTF issue: Exception definitions
Message-ID: <20010725150603.O4264@dstc.edu.au>
Reply-To: Ted McFadden <mcfadden@dstc.edu.au>
Mail-Followup-To: issues@omg.org
Mime-Version: 1.0
X-Mailer: Mutt 1.0i
Content-Type: text/plain; charset=us-ascii
X-UIDL: G`]!!J0A!!Y9E!!n\0!!

The spec defines six exceptions that carry no information other than a
text string to describe the error. This leads to cumbersome coding on
the client side.

Consider a single exception with a reason code. This conveys the same
information without requiring 5 or 6 catch blocks in some languages.

-- 
Ted McFadden
mcfadden@dstc.edu.au