Issue 3324: INS stringfied name, etc. (naming_ftf) Source: Fujitsu (Euji Yano, yano@yk.fujitsu.co.jp) Nature: Uncategorized Issue Severity: Summary: "Several points in the INS specification are not clear to me. I'd like to confirm that my understanding of these points is valid. I investigated the INS FTF document (ptc/99-12-03) and associated errata (ab/00-01-04). However, I am still not sure about the details in section "4.8.4.1 Default Resolution Order", the minor codes values in section "13.6.7 Object URLs" and the details of stringified names specified in section "4.5 Stringified Names" in the specification. The unclear points are: 1) Assume that a client program calls ORB_init with ORBInitRef (without ORBDefaultInitRef), and then calls CORBA::ORB::resolve_initial_references. A pre-configured ORB setting is used. If "1. Resolve with -ORBInitRef for this <ObjectID>" fails for any reason, must "2. Resolve with pre-configured ORB setting" be performed? I don't think so. The Client program wanted an IOR that is required by an ORB::init parameter. If the ORB returns a pre-configured IOR, then the client can't know if the returned IOR is the one that the client wanted or pre-configured IOR. 2) Is there any value defined in the specification (or other specification) about the BAD_PARAM minor codes for "BadScheme", "BadAddress" and "BadSchemeSpecificPart"? When exceptions are raised with these minor codes, exactly what's wrong with the associated URL? 3) If an escaped character in a string name is not one of '\', '/' or '.', is the string name valid? I believe it is valid. "\A\B" should be changed into "AB". 4) If a string name is empty, such as "", is the string name invalid? I believe it is invalid. If it is valid, what is the string length? 5) If the first character of string name is '/' or string name is just "/", is the string name invalid? I believe it is invalid. If it is valid, is "AAA.aaa//BBB.bbb" interpreted as: [0] "AAA", "aaa" [1] "", "" [2] "BBB", "bbb" 6) If the last character of string name is the escape character, '\', is the string name invalid? I believe it is invalid. 7) If I want to change "\\", which is not escaped yet, to an escaped string name, is the escaped string name "\\\" or "\\\\"? The "\\\" means one escape character and two escaped characters '\'. The "\\\\" means two pairs of escape character and escaped character '\'. I believe that "\\" should be changed to "\\\\". Resolution: closed. Not an issue Revised Text: Actions taken: February 14, 2000: received issue May 17, 2001: closed issue Discussion: End of Annotations:===== Date: Mon, 14 Feb 2000 10:52:16 +0900 From: Eiji Yano To: issues@omg.org, Naming FTF Cc: OD-DEVG , Masayoshi Shimamura Subject: INS stringfied name, etc. Message-Id: <38A75FD01F4.8371YANO@peacock> MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver 1.25.07 Content-Type: text/plain; charset=US-ASCII X-UIDL: /$Ce98Aod9'k(!!Q:M!! Proposed text follows: "Several points in the INS specification are not clear to me. I'd like to confirm that my understanding of these points is valid. I investigated the INS FTF document (ptc/99-12-03) and associated errata (ab/00-01-04). However, I am still not sure about the details in section "4.8.4.1 Default Resolution Order", the minor codes values in section "13.6.7 Object URLs" and the details of stringified names specified in section "4.5 Stringified Names" in the specification. The unclear points are: 1) Assume that a client program calls ORB_init with ORBInitRef (without ORBDefaultInitRef), and then calls CORBA::ORB::resolve_initial_references. A pre-configured ORB setting is used. If "1. Resolve with -ORBInitRef for this " fails for any reason, must "2. Resolve with pre-configured ORB setting" be performed? I don't think so. The Client program wanted an IOR that is required by an ORB::init parameter. If the ORB returns a pre-configured IOR, then the client can't know if the returned IOR is the one that the client wanted or pre-configured IOR. 2) Is there any value defined in the specification (or other specification) about the BAD_PARAM minor codes for "BadScheme", "BadAddress" and "BadSchemeSpecificPart"? When exceptions are raised with these minor codes, exactly what's wrong with the associated URL? 3) If an escaped character in a string name is not one of '\', '/' or '.', is the string name valid? I believe it is valid. "\A\B" should be changed into "AB". 4) If a string name is empty, such as "", is the string name invalid? I believe it is invalid. If it is valid, what is the string length? 5) If the first character of string name is '/' or string name is just "/", is the string name invalid? I believe it is invalid. If it is valid, is "AAA.aaa//BBB.bbb" interpreted as: [0] "AAA", "aaa" [1] "", "" [2] "BBB", "bbb" 6) If the last character of string name is the escape character, '\', is the string name invalid? I believe it is invalid. 7) If I want to change "\\", which is not escaped yet, to an escaped string name, is the escaped string name "\\\" or "\\\\"? The "\\\" means one escape character and two escaped characters '\'. The "\\\\" means two pairs of escape character and escaped character '\'. I believe that "\\" should be changed to "\\\\". Regards, Eiji << Eiji Yano FUJITSU LIMITED << Development Department 2, Application Server Software Division << Tel : +81-45-474-1927 Fax : +81-45-474-1954 Ext : 7124-2527 << E-Mail : yano@yk.fujitsu.co.jp @NIFTY : GDE03420