.

2 files changed, 13 insertions, 4 deletions

diff --git a/ace/Service_Manager.cpp b/ace/Service_Manager.cpp
index f5a9bd7f74a..aad3d8edf67 100644
--- a/ace/Service_Manager.cpp
+++ b/ace/Service_Manager.cpp
@@ -213,10 +213,14 @@ ACE_Service_Manager::reconfigure_services (void)
 #endif /* 0 */
 
   // Flag the main event loop that a reconfiguration should occur.
-  // The next trip through the ACE_Reactor::run_event_loop()
-  // should pick this up and cause a reconfiguration!
+  // The next trip through the <ACE_Reactor::run_event_loop> should
+  // pick this up and cause a reconfiguration.  Note that we can't
+  // trigger the reconfiguration automatically since that might "pull
+  // the rug" out from underneath the existing services in a
+  // problematic way.
   ACE_Service_Config::reconfig_occurred ((sig_atomic_t) 1);
-  return this->client_stream_.send_n ("done\n", sizeof ("done\n"));
+  return this->client_stream_.send_n ("done\n",
+                                      sizeof ("done\n"));
 }
 
 // Accept new connection from client and carry out the service they
diff --git a/ace/Service_Manager.h b/ace/Service_Manager.h
index cf75238b1c0..be40a485987 100644
--- a/ace/Service_Manager.h
+++ b/ace/Service_Manager.h
@@ -35,7 +35,12 @@ class ACE_Export ACE_Service_Manager : public ACE_Service_Object
   //     configured in an <ACE_Service_Repository>.
   //
   // = DESCRIPTION
-  //     This
+  //     This implementation is very simple.  It just handles each
+  //     client request one at a time.  Each request is associated
+  //     with a new connection, which is closed when the request is
+  //     processed.  In addition, you must be using the singleton
+  //     <ACE_Reactor::instance> in order to trigger reconfigurations.
+  //     This scheme can certainly be improved.
 public:
   // = Initialization and termination hooks.
   ACE_Service_Manager (void);