Issue 2915: Use of InvokeId as the type name for both invoke id and link id. (incorba-ftf)
Source: Ericsson (Mr. Neill Jones, etlnljs(at)etlxdmx.ericsson.se)
Nature: Uncategorized Issue
Severity: 
Summary: The idl is

    struct TcLinkedContext {
        DialogFlowCtr ctr;
        InvokeId ivk_id;
        InvokeId lnk_id;
        AssociationId a_id;
    };

While it is correct that these are both of the same type, the name of the type
could be confusing.

Resolution: 
Revised Text: 
Actions taken:
September 22, 1999: received issue
Discussion: 

End of Annotations:=====
Date: Wed, 22 Sep 1999 19:25:47 +0100
From: Neill Jones <jonesn@Teltec.DCU.IE>
Organization: Teltec DUC
X-Mailer: Mozilla 4.51 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: issues@omg.org, brennanr@Teltec.DCU.IE, jonesn@Teltec.DCU.IE
Subject: incorba-ftf
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-UIDL: ?PZd9I*He9GVLd9NSa!!

Hi all

Subject: Use of InvokeId as the type name for both invoke id and link
id.

The idl is

    struct TcLinkedContext {
        DialogFlowCtr ctr;
        InvokeId ivk_id;
        InvokeId lnk_id;
        AssociationId a_id;
    };

While it is correct that these are both of the same type, the name of
the type
could be confusing.

Regards

Neill Jones

From: "Rob Brennan" <brennanr@Teltec.DCU.IE>
To: "ftf" <incorba-ftf@omg.org>
Subject: IN/CORBA: Issue 2915
Date: Mon, 6 Dec 1999 15:01:26 -0000
X-MSMail-Priority: Normal
X-Priority: 3
X-Mailer: Microsoft Internet Mail 4.70.1154
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=ISO-8859-1
X-UIDL: b2hd9jc,e9Rh:e9XUVd9

Hi All,

this one says:

"The idl is struct TcLinkedContext { DialogFlowCtr ctr; InvokeId
ivk_id;
InvokeId lnk_id;
AssociationId a_id; }; While it is correct that these are both of the
same
type, the name of the type
could be confusing. "

Basically we declared a type InvokeId and used it for both the
ivk_id (invoke id) and lnk_id (linked id) members. This is
because a linked id is of the same type as a invoke id (in
fact it is an invoke id from a previous message).
Thus I feel that the types are the same an the IDL should
stay as it is.

rgds
rob
From: "Nilo Mitra (EUS)" <EUSNILM@am1.ericsson.se>
To: "'Rob Brennan'" <brennanr@teltec.dcu.ie>, ftf
<incorba-ftf@omg.org>
Subject: RE: IN/CORBA: Issue 2915
Date: Mon, 6 Dec 1999 09:05:22 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
X-UIDL: KFHe93g+e9I>md9D<5e9

I agree that it should stay the same as it is. I'm not confused :-)
Regards
Nilo

-----Original Message-----
From: Rob Brennan [mailto:brennanr@Teltec.DCU.IE]
Sent: Monday, December 06, 1999 10:01 AM
To: ftf
Subject: IN/CORBA: Issue 2915


Hi All,

this one says:

"The idl is struct TcLinkedContext { DialogFlowCtr ctr; InvokeId
ivk_id;
InvokeId lnk_id;
AssociationId a_id; }; While it is correct that these are both of the
same
type, the name of the type
could be confusing. "

Basically we declared a type InvokeId and used it for both the
ivk_id (invoke id) and lnk_id (linked id) members. This is
because a linked id is of the same type as a invoke id (in
fact it is an invoke id from a previous message).
Thus I feel that the types are the same an the IDL should
stay as it is.

rgds
rob