Issue 4230: Exposure of Virtual File System implementation details (ftamftp-ftf) Source: DSTC (Mr. Ted McFadden, mcfadden@dstc.edu.au) Nature: Uncategorized Issue Severity: Summary: The FTAM RFP suggested implementations take a CORBA-centric approach and hide FTAM and FTP specific details. The VirtualFileSystem interface has an attribute file_system_type that can be: FTAM, FTP, or _NATIVE. There is also a supported_content_types attribute that returns a list of FTAM file type identifiers. This seems to be exposing implementation detail a client cannot directly use. If a client cannot make use of these they should be removed from the IDL. Resolution: see above Revised Text: Actions taken: March 21, 2001: received issue Discussion: Resolution Voted to remove the following file transfer protocol specific elements from the IDL: typedef long ContentType; const ContentType FTAM_1 = 1; const ContentType FTAM_2 = 2; const ContentType FTAM_3 = 3; const ContentType FTAM_4 = 4; const ContentType FTAM_5 = 5; const ContentType NBS_9 = 6; const ContentType INTAP_1 = 7; enum NativeFileSystemType { FTAM, FTP, _NATIVE }; typedef sequence<ContentType> ContentList; readonly attribute ContentList supported_content_types; End of Annotations:===== Date: Wed, 21 Mar 2001 16:32:52 +1000 From: Ted McFadden To: issues@omg.org Subject: ftamftp-ftf issue: Exposure of Virtual File System implementation details Message-ID: <20010321163252.D26849@iona.com> Mail-Followup-To: issues@omg.org Mime-Version: 1.0 X-Mailer: Mutt 1.0i Content-Type: text/plain; charset=us-ascii X-UIDL: W`&"!O?(!!@G;e9H-hd9 Hi, ftamftp-ftf issue: Exposure of Virtual File System implementation details ------------------------------------------------------------------------- The FTAM RFP suggested implementations take a CORBA-centric approach and hide FTAM and FTP specific details. The VirtualFileSystem interface has an attribute file_system_type that can be: FTAM, FTP, or _NATIVE. There is also a supported_content_types attribute that returns a list of FTAM file type identifiers. This seems to be exposing implementation detail a client cannot directly use. If a client cannot make use of these they should be removed from the IDL. -- Ted McFadden ted.mcfadden@iona.com Object Oriented Concepts Inc. - An IONA Company http://www.orbacus.com Suite 4, 8 Martha St. +61-7-3324-9633 Camp Hill, Brisbane, 4169, QLD. Australia Date: Wed, 23 May 2001 15:00:12 +1000 From: Ted McFadden To: ftamftp-ftf@omg.org Subject: Issue 4230 Comment Message-ID: <20010523150012.H27054@iona.com> Mime-Version: 1.0 X-Mailer: Mutt 1.0i Content-Type: text/plain; charset=us-ascii X-UIDL: \'8!!R;V!!T-i!!7(h!! Issue 4230 Comment Hi, I don't believe any FTAM or FTP specific values belong in the IDL. Although I see how these values got there given the common back-ends of FTP and FTAM servers, they do not serve a useful purpose. They also imply that the only implementations will be FTAM and FTP based. I can see a number of applications for this service to perform data transfer using `files' that will not be using anything like an FTAM, FTP, or conventional file system on the backend. IONA intends to vote YES, the elements should be removed. Cheers, Ted -- Ted McFadden ted.mcfadden@iona.com IONA Total Business Integration (TM) Suite 4, 8 Martha St. +61-7-3324-9633 Camp Hill, Brisbane, 4169, QLD. Australia Date: Wed, 06 Jun 2001 18:33:45 -0400 From: Jishnu Mukerji Reply-To: jishnu_mukerji@hp.com Organization: Hewlett-Packard EIAL, Florham Park NJ, USA X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: orb_revision@omg.org Subject: Issue 4320 proposed resolution Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=iso-8859-1 X-UIDL: `f/!!]kcd98\Td9H6:e9 Status: RO The following resolution will appear in the neA character is an 8-bit quantity with a numerical value between 0 and 255 (decimal). 3.2.5.4 String Literals A string literal is a sequence of characters (as defined in Section 3.2.5.2, xt vote unless there are significant objections. Thanks, Jishnu. ____________________________________________________________________ Issue 4320: String literal definition incorrect. (orb_revision) Click here for this issue's archive. Source: Borland Software Corporation (Mr. Vijaykumar Natarajan, vijayn@borland.com vnatarajan@borland.com) Nature: Uncategorized Issue Severity: Summary: The following from the CORBA 2.4.1 specification. 3.2.5.2 Character Literal s on page 3-9) surrounded by double quotes, as inA . The above statements together implies that a string literal may contain embedded NULL characters. That is incorrect. The definition of string literals must explicitly eliminate NULL. Proposed Revised text: Section 3.2.5.4 String Literals replace this first paragraph "A string literal is a sequence of characters (as defined in Section 3.2.5.2, on page 3-9) surrounded by double quotes, as inc ." with "A string literal is a sequence of characters (as defined in Section 3.2.5.2,h on page 3-9), with the exception of the character with numeric value 0, surrounded by double quotes, as ina ." Resolution: Make it so Revised Text: In orbrev/01-03-01: In section 3.2.5.4: replace this first paragraph which reads: "A string literal is a sequence of characters (as defined in Section 3.2.5.2,r on page 3-9) surrounded by double quotes, as ina ." with: "A string literal is a sequence of characters (as defined in Section 3.2.5.2,c on page 3-9), with the exception of the character with numeric value 0, surrounded by double quotes, as int ." Actions taken: Incorporate changes and close issue er literal is one or more characters enclosed in single quotes, as in Date: Fri, 15 Jun 2001 12:10:46 +1000 From: Ted McFadden To: ftamftp-ftf@omg.org Subject: In reponse to vote on 4230, close issue 4052 without action Message-ID: <20010615121046.D7735@iona.com> Mime-Version: 1.0 X-Mailer: Mutt 1.0i Content-Type: text/plain; charset=us-ascii X-UIDL: 452e9>*5!!,*Fe9_g2e9 Since the NativeFileSystem enumeration has been removed from the IDL, issue 4052, renaming NativeFileSystem::_NATIVE to NativeFileSystem::LOCAL is no longer relevant. This will not be put to a vote unless there is an objection. Cheers, Ted -- Ted McFadden ted.mcfadden@iona.com IONA Total Business Integration (TM) Suite 4, 8 Martha St. +61-7-3324-9633 Camp Hill, Brisbane, 4169, QLD. Australia