Issue 1130:  Compacting GIOP messages by using indirections (interop)
Source:  (, )
Nature:  Revision
Severity: 
Summary: Summary: Repeated strings within an encapsulation can account
 for a large percentage of the size of the encapsulation.
 Indirections are already used in the marshaling of TypeCodes
 to allow compacting of messages.  This can be extended
 to also allow indirection for strings.  The current
 encoding of a string is the unsigned long number of characters
 in the string, followed by the null-terminated characters 
 comprising the string.  If we resolve the maximum value
 for unsigned long "0xffffffff" for indirections, the
 next byte can refer to a previously marshaled string.
 

Resolution: Close previously deferred issue as too much for RTF.  Add to GIOP future version "wish list".
Revised Text: 
Actions taken:
April 2, 1998: received issue
February 27, 2001: closed issue
Discussion: 

End of Annotations:=====
Return-Path: <goldberg@corp.borland.com>
Date: Thu, 02 Apr 1998 06:30:44 -0800
From: Jon Goldberg <goldberg@corp.borland.com>
To: interop@omg.org
CC: issues@omg.org
Subject: Compacting GIOP Messages by using indirections

Hi Folks-

Repeated strings within an encapsulation can account
for a large percentage of the size of the encapsulation.
Indirections are already used in the marshaling of TypeCodes
to allow compacting of messages.  This can be extended
to also allow indirection for strings.  The current
encoding of a string is the unsigned long number of characters
in the string, followed by the null-terminated characters 
comprising the string.  If we resolve the maximum value
for unsigned long "0xffffffff" for indirections, the
next byte can refer to a previously marshaled string.

-Jon

Return-Path: <michi@dstc.edu.au>
X-Authentication-Warning: tigger.dstc.edu.au: michi owned process
doing -bs
Date: Fri, 3 Apr 1998 06:10:54 +1000 (EST)
From: Michi Henning <michi@dstc.edu.au>
To: Jon Goldberg <goldberg@corp.borland.com>
cc: interop@omg.org, issues@omg.org
Subject: Re: Compacting GIOP Messages by using indirections

On Thu, 2 Apr 1998, Jon Goldberg wrote:

> Repeated strings within an encapsulation can account
> for a large percentage of the size of the encapsulation.
> Indirections are already used in the marshaling of TypeCodes
> to allow compacting of messages.  This can be extended
> to also allow indirection for strings.  The current
> encoding of a string is the unsigned long number of characters
> in the string, followed by the null-terminated characters 
> comprising the string.  If we resolve the maximum value
> for unsigned long "0xffffffff" for indirections, the
> next byte can refer to a previously marshaled string.

I take it you mean a previously marshalled string in the same message?

If so, I don't think the optimization gains much. How often do I send
paramaters to an operation that contain the same string value more
than
one? Not very often I bet.

							Cheers,

								Michi.
--
Michi Henning              +61 7 33654310
DSTC Pty Ltd               +61 7 33654311 (fax)
University of Qld 4072     michi@dstc.edu.au
AUSTRALIA
http://www.dstc.edu.au/BDU/staff/michi-henning.html