From 8b141bcbc058e812f39a5bc328c76233f79d2469 Mon Sep 17 00:00:00 2001 From: schmidt Date: Tue, 17 Jun 2008 13:45:08 +0000 Subject: ChangeLogTag:Mon --- TAO/ChangeLog | 6 ++++++ TAO/docs/configurations.html | 8 ++------ 2 files changed, 8 insertions(+), 6 deletions(-) diff --git a/TAO/ChangeLog b/TAO/ChangeLog index af125cda626..e291b17e93d 100644 --- a/TAO/ChangeLog +++ b/TAO/ChangeLog @@ -1,3 +1,9 @@ +Tue Jun 17 13:37:09 UTC 2008 Douglas C. Schmidt + + * docs/configurations.html: Zapped the discussion of GIOPlite + since it's no longer supported. Thanks to Abdul Sowayan for + reporting this. + Tue Jun 17 09:30:00 UTC 2008 Simon Massey * TAO_IDL/contrib/mcpp/main.cpp: diff --git a/TAO/docs/configurations.html b/TAO/docs/configurations.html index 34c949f585d..c5d2dc5fa1c 100644 --- a/TAO/docs/configurations.html +++ b/TAO/docs/configurations.html @@ -783,17 +783,13 @@ Configuration for Homogenous Systems

  • Run-time options -

    If the only ORB running is TAO and there is no need to be - IIOP interoperable the option -ORBGIOPlite can be used - to reduce the message size and the processing time.

    Unix systems that support local IPC (formerly known as Unix domain sockets) can take advantage of TAO's UIOP pluggable transport protocol to improve performance considerably. To use TAO's UIOP pluggable protocol, simply specify a UIOP endpoint on the command line using the -ORBEndpoint option described in the - options documentation. Further performance - improvement can be achieved by using the UIOP protocol in combination - with the -ORBGIOPlite option. Additional information about + options documentation. Additional + information about TAO's UIOP pluggable protocol can be found in the release notes.

    -- cgit v1.2.1