diff options
Diffstat (limited to 'TAO/tao/Transport.h')
| -rw-r--r-- | TAO/tao/Transport.h | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/TAO/tao/Transport.h b/TAO/tao/Transport.h index 5a768714b81..52f6976eb38 100644 --- a/TAO/tao/Transport.h +++ b/TAO/tao/Transport.h @@ -244,14 +244,14 @@ namespace TAO * - Minimize locking and copying overhead when trying to attack the * above. * - * <H3> Parsing messages (GIOP) & processing the message:</H3> + * <H3>Parsing messages (GIOP) & processing the message:</H3> * * The messages should be checked for validity and the right * information should be sent to the higher layer for processing. The * process of doing a sanity check and preparing the messages for the * higher layers of the ORB are done by the messaging protocol. * - * <H3> Design forces and Challenges </H3> + * <H3>Design forces and Challenges </H3> * * To keep things as efficient as possible for medium sized requests, * it would be good to minimize data copying and locking along the @@ -293,7 +293,7 @@ namespace TAO * message from the queue and processes that. Once the queue * is drained the last thread resumes the handle. * - * <H3> Sending Replies </H3> + * <H3>Sending Replies </H3> * * We could use the outgoing path of the ORB to send replies. This * would allow us to reuse most of the code in the outgoing data @@ -304,7 +304,7 @@ namespace TAO * Reactor could potentially handle other messages (incoming or * outgoing) and the stack starts growing leading to crashes. * - * <H4> Solution to the nesting problem </H4> + * <H4>Solution to the nesting problem </H4> * * The solution that we (plan to) adopt is pretty straight * forward. The thread sending replies will not block to send the |