Issues for Externalization Working Group of the CORBAservices RTFmailing list

To comment on any of these issues, send email to externalization@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 19: Stream contexts and internalization
Issue 20: Start and end of context tags
Issue 21: Definition of stream portability
Issue 22: Multiple objects on a stream
Issue 466: Common format on stream
Issue 476: CosCompoundExternalization Service
Issue 477: CosCompoundExternalization Service (2)
Issue 478: CosCompoundExternalization Service (3)
Issue 706: Internalizing roles-IDL optimization
Issue 1401: Circular References in CosStream and CosCompoundExternalization

Issue 19: Stream contexts and internalization (externalization)

Click here for this issue's archive.
Nature: Uncategorized
Severity:
Summary:
Summary: The Externalization spec does not state how a stream implementation is to discover that a context exists when internalizing an object.

Resolution:
Revised Text:
Actions taken:
June 26, 1996: Received issue

Discussion:


Issue 20: Start and end of context tags (externalization)

Click
here for this issue's archive.
Nature: Uncategorized
Severity:
Summary:
Summary: The standard stream data format does not define tags to be used to identify the beginning and end of a context.

Resolution:
Revised Text:
Actions taken:
June 26, 1996: Received issue

Discussion:


Issue 21: Definition of stream portability (externalization)

Click
here for this issue's archive.
Nature: Uncategorized
Severity:
Summary:
Summary: The standard stream format should specify that it is portable across different ORBs and hardware, but not across streamable object implementations whch use different semantic content.

Resolution:
Revised Text:
Actions taken:
June 26, 1996: Received issue

Discussion:


Issue 22: Multiple objects on a stream (externalization)

Click
here for this issue's archive.
Nature: Uncategorized
Severity:
Summary:
Summary: What happens when multiple calls are made to Stream::externalize() at the top level? Does the stream contain all those objects, and how does a client discover this?

Resolution:
Revised Text:
Actions taken:
June 26, 1996: Received issue

Discussion:


Issue 466: Common format on stream (externalization)

Click
here for this issue's archive.
Nature: Uncategorized
Severity:
Summary:
Summary: When reading a stream, there is no way of telling where context (limited to calls to begin_context and end_context) end and a new one starts.. Resolved problem with new "tag-byte" 0xFF.

Resolution:
Revised Text:
Actions taken:
December 19, 1996: received issue

Discussion:


Issue 476: CosCompoundExternalization Service (externalization)

Click
here for this issue's archive.
Nature: Uncategorized
Severity:
Summary:
Summary: When Node::externalize_node is called, is node responsible for externalizing related object? What happens, if related object isn"t a CosStream::Streamable?

Resolution:
Revised Text:
Actions taken:
January 21, 1997: received issue

Discussion:


Issue 477: CosCompoundExternalization Service (2) (externalization)

Click
here for this issue's archive.
Nature: Uncategorized
Severity:
Summary:
Summary: Role in new node are disconnected It"s role of read_graph to correctly establish new relationships. How is that accomplished?

Resolution:
Revised Text:
Actions taken:
January 21, 1997: received issue

Discussion:


Issue 478: CosCompoundExternalization Service (3) (externalization)

Click
here for this issue's archive.
Nature: Uncategorized
Severity:
Summary:
Summary: When internalizing a relationships, how do the "shallow" nodes and roles get included?

Resolution:
Revised Text:
Actions taken:
January 21, 1997: received issue

Discussion:


Issue 706: Internalizing roles-IDL optimization (externalization)

Click
here for this issue's archive.
Nature: Uncategorized
Severity:
Summary:
Summary: The IDL for internalizing roles could be optimized to reduce the size of the externalized data as well as simplifying the implementation

Resolution:
Revised Text:
Actions taken:
August 25, 1997: received issue

Discussion:


Issue 1401: Circular References in CosStream and CosCompoundExternalization (externalization)

Click
here for this issue's archive.
Nature: Uncategorized Issue
Severity:
Summary:
Summary: Circular refrences to CosStream and CosCompoundExternalization,
 i have not been able to find an idl compiler that can compile
 these modules.
 
 as aside, i have foud many syntax errors in the IDL you provide
 as CORBAServices98-03-02.idl, in many of its interfaces, there are
 typos, and it is not correct with the specifications.
 

Resolution:
Revised Text:
Actions taken:
June 1, 1998: received issue

Discussion: