Issue 1131:  Compacting GIOP Messages by using templates (interop)
Source:  (, )
Nature:  Revision
Severity: 
Summary: Summary: A common server pattern is that of "factory".  As a result
 of a request, a Factory returns an object reference.
 Frequently, these object references differ only by a
 small fraction of their full size.  For example, object
 references may be exactly the same except for the object_key
 member of a GIOP profile and maybe the repository_id field
 of the IOR.  Allowing the factory to return a more compact
 representation of the object reference would yield great
 savings in message size.
 If the server or client can establish a template for filling 
 out object references (or possibly any type of data), a 
 more compact on-the-wire form can be used for such object
 references once the template is established.
 

Resolution: Close this previously deferred issue as too much for RTF.  Add to GIOP future version "wish list" do
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:31:41 -0800
From: Jon Goldberg <goldberg@corp.borland.com>
To: interop@omg.org
CC: issues@omg.org
Subject: Compacting GIOP Messages by using templates

Hi Folks-

A common server pattern is that of "factory".  As a result
of a request, a Factory returns an object reference.
Frequently, these object references differ only by a
small fraction of their full size.  For example, object
references may be exactly the same except for the object_key
member of a GIOP profile and maybe the repository_id field
of the IOR.  Allowing the factory to return a more compact
representation of the object reference would yield great
savings in message size.
If the server or client can establish a template for filling 
out object references (or possibly any type of data), a 
more compact on-the-wire form can be used for such object
references once the template is established.

-Jon