Skip to content

[BZ-1529] GIOP_Message_Base::write_protocol_header needs to be more efficient #1529

@jwillemsen

Description

@jwillemsen
Field Value
Bugzilla ID 1529
Reporter Nanbor Wang
Assigned to DOC Center Support List (internal)
Product TAO
Component ORB
Version 1.3.2
Platform / OS All / All
Priority P3
Severity normal
Status ASSIGNED
Resolution
Created 2003-06-09 22:55:39 -0500

Originally posted by Nanbor Wang on 2003-06-09 22:55:39 -0500


Few points for making it efficient

  1. The call reset () on the CDR should be removed and its a waste since we only
    use a fresh CDR

  2. The GIOP class should cache a CDR stream with the GIOP header written the
    first time. This is perfectly valid

    • the client holds a lock on the transport and so you can use the cached
      version with the same header again and again

    • the server needs to asses the GIOP minor revision before sending the reply
      out and its a single write operation after indexing to the right position.

for #2 to be possible the ACE/TAO_OutputCDR streams need to have a way to chain
CDR streams or the internal message blocks.

This should save CPU cycles in the outgoing path.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions