ChangeLogTag:Tue Mar 28 14:40:54 2000 Carlos O'Ryan <coryan@uci.edu>

1 files changed, 20 insertions, 15 deletions

diff --git a/TAO/tao/target_specification.h b/TAO/tao/target_specification.h
index 59b1268fee0..2e07be74abd 100644
--- a/TAO/tao/target_specification.h
+++ b/TAO/tao/target_specification.h
@@ -11,8 +11,8 @@
 //
 // = DESCRIPTION
 //    A class that encapsulates the target identification details.
-//    
-//    
+//
+//
 // = AUTHOR
 //     Balachandran  Natarajan <bala@cs.wustl.edu>
 // ============================================================================
@@ -32,12 +32,12 @@ class TAO_Target_Specification
   //
   // = DESCRIPTION
   //   @@ Bala: do we have examples of how other protocols map object
-  //      keys?  
+  //      keys?
   //   @@ Carlos: The way HTTP-NG does is not quite intuitive. But
   //      they too have a sequnce of Octet which more or less fits this
   //      model. You are also allowed to specify is a Cache Index (14
   //      bits). I think that can also be worked out and shouldn't be
-  //      a big deal.  
+  //      a big deal.
   //   @@ Bala:What if they pass something around that does not fit
   //      this model?
   //   @@ Carlos:As long as we dont know it is ok. But then if we get
@@ -48,7 +48,12 @@ class TAO_Target_Specification
   //      I can look ahead possibily a couple of days but not a life
   //      time  :-) But you have a good question though. Please sont
   //      remove these discussions. It could be useful for someone
-  //      someday. 
+  //      someday.
+
+  //   @@ Bala: i hate to be picky on these matters, but you are not
+  //   writing a novel or your memoirs, 'I foresee' does not look like
+  //   the right kind of comment in a class description.
+  //
   //   The motivation behind this is GIOP 1.2 althought I foresee
   //   other messaging protocols doing something similar.
   //   The Invocation classes (client side) were
@@ -59,9 +64,9 @@ class TAO_Target_Specification
   //   key. They can send send the IOP::TaggedProfile or IOP::IOR
   //   profile. So I am putting these possibilites in this class and
   //   pass it to the messaging layer. It would extract what is
-  //   required. 
+  //   required.
 public:
-  
+
   TAO_Target_Specification (void);
   // Ctor
   enum TAO_Target_Address
@@ -74,7 +79,7 @@ public:
 
   // Note: Please do not pass in a identifiers that is allocated on
   // stack. These methods does not make a copy but holds the pointer
-  // passed in. 
+  // passed in.
   void target_specifier (const TAO_ObjectKey &key);
   // Set the target specification by giving the object key.
 
@@ -82,7 +87,7 @@ public:
   void target_specifier (IOP::TaggedProfile *profile);
   // Set the target specification by passing in an IOP::TaggedProfile.
 
-  void target_specifier (IOP::IOR *ior, 
+  void target_specifier (IOP::IOR *ior,
                          CORBA::ULong prof_index);
   // Specify the target by passing in the IOP::IOR with a profile
   // index. Please see the header file IOPC.h on why a profile index
@@ -93,21 +98,21 @@ public:
   // Returns the object key after a check of the stored specifier. If
   // the stored specifier is not of the right type then this would
   // return a NULL
-  
+
   const IOP::TaggedProfile *profile (void);
   // Returns the IOP::TaggedProfile after a check of the stored specifier. If
   // the stored specifier is not of the right type then this would
   // return a NULL
-  
+
   CORBA::ULong iop_ior (IOP::IOR *&ior);
   // Returns a  pointer to IOP::IOR through the parameters and the
   // index of the selected profile as a return parameter after a check
   // of the stored specifier. If the stored specifier is not of the
-  // right type then this would return a NULL. 
-  
+  // right type then this would return a NULL.
+
   TAO_Target_Address specifier (void);
   // Access the TArget_Address specifier
-  
+
 private:
   union
   {
@@ -116,7 +121,7 @@ private:
     IOP::IOR *ior_;
   } u_;
   // The union of all the possibilities
-  
+
   TAO_Target_Address specifier_;
   // The enum identifier