Issue 3877: module IOP_N needs a real name (orb_revision) Source: Oracle (Dr. Harold Carr, Ph.D., nobody) Nature: Uncategorized Issue Severity: Summary: The interceptors specification, ptc/00-08-06, defines: IOP_N Issue: "_N" needs to be replaced with the correct version such that this module has a real name. Resolution: Revised Text: Requires special handling while merging ptc/00-08-06 changes into the mainline Core 2.4 in order to get Core 3.0. The instructions in the Resolution section will suffice quite unambiguously on what needs to be done in the merge process. Actions taken: September 19, 2000: received issue February 27, 2001: closed issue Discussion: _N should be replaced by the null string, i.e. whatever is in IOP_N in ptc/00-08-06 should be appended to the IOP module. End of Annotations:===== Date: Tue, 19 Sep 2000 19:34:31 -0700 (PDT) Message-Id: <200009200234.TAA27472@shorter.eng.sun.com> From: Harold Carr To: issues@omg.org, orb_revision@omg.org Subject: module IOP_N needs a real name Content-Type: text X-UIDL: b91!!%Z\!!n'I!!O"(!! This is a core issue. The interceptors specification, ptc/00-08-06, defines: IOP_N Issue: "_N" needs to be replaced with the correct version such that this module has a real name. Date: Wed, 18 Oct 2000 15:17:11 -0400 From: Jishnu Mukerji Reply-To: jis@fpk.hp.com Organization: Hewlett-Packard EIAL, Florham Park NJ USA X-Mailer: Mozilla 4.73 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: orb_revision@omg.org Subject: Issue 3877 proposed resolution Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-UIDL: *]ld9Uf)!!O&8e9^Xm!! Following will be included in the next vote: Issue 3877: module IOP_N needs a real name (orb_revision) Click here for this issue's archive. Source: Sun Microsystems (Dr. Harold Carr, Ph.D., harold.carr@sun.com) Nature: Uncategorized Issue Severity: Summary: The interceptors specification, ptc/00-08-06, defines: IOP_N Issue: "_N" needs to be replaced with the correct version such that this module has a real name. Resolution: _N should be replaced by the null string, i.e. whatever is in IOP_N in ptc/00-08-06 should be appended to the IOP module. Revised Text: Requires special handling while merging ptc/00-08-06 changes into the mainline Core 2.4 in order to get Core 3.0. The instructions in the Resolution section will suffice quite unambiguously on what needs to be done in the merge process. Actions taken: Incorporate changes and close issue ___________________________________________________________________ Comments? Jishnu. -- Jishnu Mukerji Senior Systems Architect, EIAL Hewlett-Packard Company 300 Campus Drive, MS 2E-62 Florham Park NJ 07932, USA +1 973 443 7528 jis@fpk.hp.com Date: Wed, 18 Oct 2000 12:43:27 -0700 From: Harold Carr X-Mailer: Mozilla 4.51 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: jis@fpk.hp.com CC: orb_revision@omg.org Subject: Re: Issue 3877 proposed resolution References: <39EDF737.ED575EAD@fpk.hp.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-UIDL: LdBe9JYIe92KK!!W4W!! > Issue 3877: module IOP_N needs a real name (orb_revision) > Resolution: _N should be replaced by the null string, i.e. whatever is > in IOP_N in ptc/00-08-06 should be appended to the IOP module. There was a short discussion of this in interceptors-ftf. All the PI implementors that responded said they have already put what was specified to be in IOP_N in IOP. So, yes, IOP is the right place. Cheers, Harold