Wed Jun 27 22:02:03 2001 Chris Cleeland <cleeland_c@ociweb.com>

2 files changed, 71 insertions, 61 deletions

diff --git a/TAO/ChangeLogs/ChangeLog-02a b/TAO/ChangeLogs/ChangeLog-02a
index 37c67b32548..f11ddddc7df 100644
--- a/TAO/ChangeLogs/ChangeLog-02a
+++ b/TAO/ChangeLogs/ChangeLog-02a
@@ -1,3 +1,8 @@
+Wed Jun 27 22:02:03 2001  Chris Cleeland  <cleeland_c@ociweb.com>
+
+	* orbsvcs/Naming_Service/README: Updated this to reflect the fact
+ 	that multicast response is no longer the default.
+
 Wed Jun 27 14:25:48 2001  Chris Cleeland  <cleeland_c@ociweb.com>
 
 	* tao/PortableServer/Operation_Table.cpp (find): Enhanced the
diff --git a/TAO/orbsvcs/Naming_Service/README b/TAO/orbsvcs/Naming_Service/README
index 4ea7c294f64..4112caf05dc 100644
--- a/TAO/orbsvcs/Naming_Service/README
+++ b/TAO/orbsvcs/Naming_Service/README
@@ -19,14 +19,15 @@ The following describes how to run the TAO Naming Service.
                          [-t time]
                          [-f persitence_file_name]
                          [-b base_address]
-			 [-m (1=enable multicast(default),0=disable]
+			 [-m (1=enable multicast responses,0=disable(default)]
 
 2. Optional Command-line Arguments
 
         -ORBNameServicePort nsport
                 Multicast port for listening for requests from clients
                 trying to bootstrap to a Naming Service through the
-                use of multicast.
+                use of multicast.  This is only used when multicast
+                responding is enabled via '-m 1'.
 
         -o ior_output_file
                 The name of the file, in which to store the IOR of the
@@ -59,21 +60,22 @@ The following describes how to run the TAO Naming Service.
                 in persistent mode, i.e., "-f" option is present.
 
 	-m <0|1>
-		By default the Naming Service will respond to
-		multicast queries.  This is a non-standard but very
-		simple way to discover the Naming Service in TAO.
-		In real applications the multicast lookup mechanism
-		can be innadequate, for example, if there are multiple
-		naming services running on the network.
-		In such cases the Interoperable Naming Service
-		bootstrap options are a better choice.
+                TAO offers a simple, very non-standard method for
+                clients to discover the initial reference for the
+                Naming Service.  However, since it can be innadequate and cause
+		unexpected results if, for example, there are multiple
+		naming services running on the network, the DEFAULT
+		behavior is for the Naming Service to NOT RESPOND to
+		such multicast queries (use the Interoperable Naming
+		Service bootstrap options instead).
 
 3. Environment Variables
 
         NameServicePort
                 Multicast port for listening for requests from clients
                 trying to bootstrap to a Naming Service through the
-                use of multicast.
+                use of multicast.  This is only used when multicast
+                responding is enabled via '-m 1'.
 
 4. Persistence
 
@@ -141,56 +143,9 @@ The following describes how to run the TAO Naming Service.
         There are several methods for a client to bootstrap to a
         Naming Service, i.e., there are several mechanisms
         <resolve_initial_references> can use when asked for
-        "NameService".
-
-        1. Multicast
-
-                By default (unless other options are specified - see
-                items 2 and 3 below), ip multicast is used to locate a
-                Naming Service. TAO Naming Server is listening for
-                client multicast requests on a specified port.  On the
-                client side, <resolve_initial_references> sends out a
-                multicast request on the network, trying to locate a
-                Naming Service.  When a Naming Server receives a
-                multicast request from a client, it replies to the
-                sender with the ior of its root Naming Context.  Note,
-                the port used for this bootstrapping process, i.e.,
-                'multicast port', has nothing to do with the ORB port
-                used for CORBA communication.  Other points worth
-                mentioning:
+        "NameService".  In order of predictable behavior, they are:
 
-                - A client and a server will only click through this
-                  multicast protocol if they are using the same
-                  multicast port.  For both client and server
-                  -ORBnameserviceport command-line option and
-                  NameServicePort environment variable can be used to
-                  specify the multicast port to use.  If none is
-                  specified, the default port is used.  (The ability
-                  to specify multicast ports can be used to match
-                  certain clients with certain Naming Servers, when
-                  there are more than one Naming Server running on the
-                  network).
-
-                - If there are several Naming Servers running on the
-                  network, each listening on the same port for
-                  multicast requests, each will send a reply to a
-                  client's request.  The client's orb will use the
-                  first response it receives, so the Naming Service
-                  will, in fact, be selected at random.
-
-                Since this mechanism is proprietary to TAO (i.e.,
-                non-standard), it only works when both client and
-                server are written using TAO.  There is no way to turn
-                multicasting off, but it is used only as a last
-                resort, i.e., any of the options below will override
-                it.
-
-                When OS platform doesn't support multicast, or client
-                or server isn't written using TAO, or a more reliable
-                location method is desired, etc., one of the options
-                below can be used to bootstrap to the Naming Service.
-
-        2. Command-line options
+        1. Command-line options
 
                 The "-ORBInitRef NameService=IOR:..." or environment
                 variable NameServiceIOR can be used on the client side
@@ -211,7 +166,7 @@ The following describes how to run the TAO Naming Service.
                         should return for the Naming Service in a file
                         format.
 
-        3. Interoperable Naming Service.
+        2. Interoperable Naming Service.
 
                 TAO implements the standard CORBA Interoperable Naming
                 Service (ING).  Therefore, most initialization options
@@ -219,6 +174,56 @@ The following describes how to run the TAO Naming Service.
                 Service (see TAO's releasenotes for the status of INS
                 implementation).
 
+        3. Multicast
+
+                When started with the "respond to multicast queries"
+                option turned on ('-m 1'), clients can use IP
+                multicast to query for a Naming Service, and this
+                instance will respond. TAO Naming Server is listening
+                for client multicast requests on a specified port.  On
+                the client side, <resolve_initial_references> sends
+                out a multicast request on the network, trying to
+                locate a Naming Service.  When a Naming Server
+                receives a multicast request from a client, it replies
+                to the sender with the ior of its root Naming Context.
+                Note, the port used for this bootstrapping process,
+                i.e., 'multicast port', has nothing to do with the ORB
+                port used for CORBA communication.  Other points worth
+                mentioning:
+
+                - A client and a server will only click through this
+                  multicast protocol if they are using the same
+                  multicast port.  For both client and server
+                  -ORBnameserviceport command-line option and
+                  NameServicePort environment variable can be used to
+                  specify the multicast port to use.  If none is
+                  specified, the default port is used.  (The ability
+                  to specify multicast ports can be used to match
+                  certain clients with certain Naming Servers, when
+                  there are more than one Naming Server running on the
+                  network).
+
+                - If there are several Naming Servers running on the
+                  network, each listening on the same port for
+                  multicast requests, each will send a reply to a
+                  client's request.  The client's orb will use the
+                  first response it receives, so the Naming Service
+                  will, in fact, be selected at random.
+
+                Since this mechanism is proprietary to TAO (i.e.,
+                non-standard), it only works when both client and
+                server are written using TAO.  There is no way to turn
+                multicasting off on the client side, but it is used
+                only as a last resort, i.e., any of the other options
+                will override it.
+
+                When OS platform doesn't support multicast, or client
+                or server isn't written using TAO, or a more
+                reliable/predictable location method is desired, etc.,
+                one of the other options can be used to bootstrap to
+                the Naming Service.
+
+
 How to use the NT_Naming_Service
 ================================