Issue 4309: Incorrect text in 15.4.6.2 (interop)
Source: Triodia Technologies Pty Ltd (Mr. Michi Henning, michi(at)triodia.com)
Nature: Uncategorized Issue
Severity: 
Summary: 15.4.6.2, "LocateReplyBody" says:

	In GIOP version 1.0 and 1.1, Locate reply bodies are marshaled into
	the CDR encapsulation of the containing Message immediately following
	the Reply Header. In GIOP version 1.2, the Reply Body is always
	aligned on an 8-octet boundary. The fact that GIOP specifies the
	maximum alignment for any primitive type is 8 guarantees that
	the ReplyBody will not require remarshaling if the Locate Reply
	Header are modified.

The final sentence doesn't make sense because the LocateReply header is
a fixed-length header and therefore can't possibly cause remarshalling.

I suggest to delete the final sentence of this para.
Resolution: see resolution of Urgent Issue 4314
Revised Text: 
Actions taken:
May 16, 2001: received issue
October 3, 2001: closed issue
Discussion: 

End of Annotations:=====
Date: Wed, 16 May 2001 09:58:13 +1000 (EST)
From: Michi Henning <michi.henning@iona.com>
Reply-To: Interoperability RTF <interop@omg.org>
To: Interoperability RTF <interop@omg.org>
cc: issues@omg.org
Subject: Incorrect text in 15.4.6.2
Message-ID: <Pine.HPX.4.05.10105160953540.3940-100000@bobo.ooc.com.au>
Organization: IONA Technologies
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-UIDL: iEpd97UA!!FiI!!47od9

Hi, 15.4.6.2, "LocateReplyBody" says:

    In GIOP version 1.0 and 1.1, Locate reply bodies are marshaled
    into
    the CDR encapsulation of the containing Message immediately
    following
    the Reply Header. In GIOP version 1.2, the Reply Body is always
    aligned on an 8-octet boundary. The fact that GIOP specifies the
    maximum alignment for any primitive type is 8 guarantees that
    the ReplyBody will not require remarshaling if the Locate Reply
    Header are modified.

The final sentence doesn't make sense because the LocateReply header
is
a fixed-length header and therefore can't possibly cause
remarshalling.

I suggest to delete the final sentence of this para.

				       Cheers,

											Michi.
--
Michi Henning                             +61 7 3324 9633
Chief CORBA Scientist                     +61 4 1118 2700 (mobile)
IONA Technologies                         +61 7 3324 9799 (fax)
Total Business Integration
http://www.ooc.com.au/staff/michi

X-Authentication-Warning: emerald.omg.org: hobbit.omg.org
[192.67.184.3] didn't use HELO protocol
Received: from operation.dublin.iona.ie (212.120.147.5) by
hobbit.omg.org asmtp(1.0)
	       id 9379; Wed, 16 May 2001 05:42:32 -0400 (EDT)
Received: from eggs (eggs.dublin.emea.iona.com [212.120.147.19]) by
dublin.iona.ie (8.8.8/iona-1.02) with ESMTP id KAA19336 for
<interop@omg.org>; Wed, 16 May 2001 10:38:29 +0100 (BST)
Message-Id: <200105160938.KAA19336@dublin.iona.ie>
To: Interoperability RTF <interop@omg.org>
Subject: Re: Incorrect text in 15.4.6.2 
Date: Wed, 16 May 2001 10:50:13 +0100
From: Craig Ryan <cryan@iona.com>
Content-Type: text
X-UIDL: *,=!!O2?!!/L_d9VYZd9


>Hi, 15.4.6.2, "LocateReplyBody" says:
>
>	In GIOP version 1.0 and 1.1, Locate reply bodies are marshaled
>into
>	the CDR encapsulation of the containing Message immediately
>following
>	the Reply Header. In GIOP version 1.2, the Reply Body is
>always
>	aligned on an 8-octet boundary. The fact that GIOP specifies
>the
>	maximum alignment for any primitive type is 8 guarantees that
>	the ReplyBody will not require remarshaling if the Locate
>Reply
>	Header are modified.
>
>The final sentence doesn't make sense because the LocateReply header
>is
>a fixed-length header and therefore can't possibly cause
>remarshalling.
>
>I suggest to delete the final sentence of this para.

also, minor change of 'Reply Body' and 'Reply Header' to 'Locate Reply
Body' and 'Locate Reply Header'.

regards,
craig.