Bug 3059

Summary:	Split sending protocol header and request/reply header in GIOP_Message_Base
Product:	TAO	Reporter:	Johnny Willemsen <jwillemsen>
Component:	ORB	Assignee:	DOC Center Support List (internal) <tao-support>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	P3
Version:	1.5.10
Hardware:	All
OS:	All
Bug Depends on:
Bug Blocks:	2623

Description Johnny Willemsen 2007-08-22 09:30:25 CDT

at this moment the invocation code calls for example generate_request_header on the GIOP_Message_Base but if we want to make it possible to compress all data after the protocol header, the interface of the GIOP_Message_Base (also pluggable messaging) has to change to make this possible. 

Steps we then do:
* write the protocol header
* marshal the request/reply header with the data in a different stream
* compress the second stream, if smaller, use that to send out, or send the original stream

Comment 1 Johnny Willemsen 2007-08-22 10:47:23 CDT

will impact lot of pluggable messaging api's.

Comment 2 Johnny Willemsen 2007-09-21 05:44:05 CDT

pluggable messaging abstraction has been removed, changing this will now be much easier

Comment 3 Johnny Willemsen 2008-06-20 13:13:25 CDT

not needed anymore, ideas on what to compress have changed, also the streams can be used much more efficient then this