readme

这是广泛使用的通信开源项目,对于大容量,高并发的通讯要求完全能够胜任,他广泛可用于网络游戏医学图像网关的高qos要求.更详细的内容可阅读相应的材料

README,v 1.2 2000/09/07 01:14:49 marina Exp

This is a unit test for RTCORBA::ServerProtocolPolicy.

Scenario:
--------
The server first prints out its ORB default Server Protocol policy.
If the <-p> command line option was specified, a child POA is created
and configured with Server Protocol Policy containing a single
protocol specified with <-p> (see options section below).
The object is registered with child POA if one was created (root poa
otherwise) and the server waits for requests.
The client obtains server IOR and makes a single incocation, causing
server process to shut down its orb and exit.

To run (on Unix):
-------
$./server [-o <ior_file> -p <profile_id>]
$./client [-k <ior>]


Options:
--------
         Server:

-o <ior_output_file>   Default: test.ior
                       Filename for output of server's IOR.

-p <profile_id>        Default: none.
                       The POA with which the object will be
                       registered will be configured with Server
                       Protocol Policy cotaining a single protocol -
                       the one identified by <profile_id>.  If this
                       option is not present, then the POA is not
                       configured with Server Protocol Policy and ORB
                       default is used.

         Client:

-k <server_ior>        Default: file://test.ior
                       Server's IOR

Expected output:
----------------
Expected output varies with the configurations used to run the test.
General guidelines:

1) ORB default ServerProtocolPolicy must contain all the protocols
   that were loaded in the order they were loaded.  This can be
   manipulated through the use of service config files (see run_test.pl)

2) Run client with -ORBdebuglevel 1 to see which protocol is used for
   communication.  Make sure it is the same protocol that was
   specified with <-p> or the first available from orb default server
   protocol policy if <-p> wasn't specified (see run_test.pl for
   sample options)

3) See OMG Real-Time CORBA specification and TAO's Real-Time CORBA
   documentation for more information.


Sample Run/Output (on Unix):
----------------
* Server:

$./server -ORBendpoint iiop:// -ORBendpoint uiop:// -ORBendpoint \
shmiop:// -p 1413566210

ORB default for ServerProtocolPolicy contains 3 protocols:
  Protocol 0: IOP::ProfileId = 0
     Properties:
      send_buffer_size = 65536
      receive_buffer_size = 65536
      no_delay = 1
  Protocol 1: IOP::ProfileId = 1413566208
     Properties:
      send_buffer_size = 65536
      receive_buffer_size = 65536
  Protocol 2: IOP::ProfileId = 1413566210

Activated as <IOR:000000000000000d49444c3a546573743a312e30000000000000000154414f020000008000010200000000116163652e63732e777573746c2e6564750000cbef0000002314010f004e535439b59013000388560000000100000001000000000000000100000001000000000300000000000000080000000054414f000000000100000014000000000001000100000000000101090000000054414f000000000400000000>

Received request to shut down the ORB
Server ORB event loop finished


* Client (in a separate window):

$./client -ORBdebuglevel 1
TAO (20145|1) Loaded default protocol <IIOP_Factory>
TAO (20145|1) Loaded default protocol <UIOP_Factory>
TAO (20145|1) Loaded default protocol <SHMIOP_Factory>
TAO (20145|1) SHMIOP connection to server <127.0.0.1:52207> on 8