[Boost-commit] svn:boost r39529 - sandbox/thread_safe_signals/libs/thread_safe_signals/doc

From: fmhess_at_[hidden]
Date: 2007-09-25 15:17:51

Author: fmhess
Date: 2007-09-25 15:17:48 EDT (Tue, 25 Sep 2007)
New Revision: 39529
URL: http://svn.boost.org/trac/boost/changeset/39529

Log:
Description of connection class implementation doesn't apply 
to thread_safe_signals.

Text files modified: 
   sandbox/thread_safe_signals/libs/thread_safe_signals/doc/design.xml |    27 ---------------------------             
   1 files changed, 0 insertions(+), 27 deletions(-)

Modified: sandbox/thread_safe_signals/libs/thread_safe_signals/doc/design.xml
==============================================================================
--- sandbox/thread_safe_signals/libs/thread_safe_signals/doc/design.xml	(original)
+++ sandbox/thread_safe_signals/libs/thread_safe_signals/doc/design.xml	2007-09-25 15:17:48 EDT (Tue, 25 Sep 2007)
@@ -8,33 +8,6 @@
   <using-namespace name="boost::signals"/>
 
   <section>
-    <title><code>connection</code> class</title>
-
-    <para> The <code><classname>connection</classname></code> class is
-    central to the behavior of the Boost.Signals library. It is the
-    only entity within the Boost.Signals system that has knowledge of
-    all objects that are associated by a given connection. To be
-    specific, the <code><classname>connection</classname></code> class
-    itself is merely a thin wrapper over a
-    <code><classname>shared_ptr</classname></code> to a
-    <code>basic_connection</code> object.</para>
-
-    <para> <code><classname>connection</classname></code> objects are
-    stored by all participants in the Signals system: each
-    <code><classname>trackable</classname></code> object contains a
-    list of <code><classname>connection</classname></code> objects
-    describing all connections it is a part of; similarly, all signals
-    contain a set of pairs that define a slot. The pairs consist of a
-    slot function object (generally a Boost.Function object) and a
-    <code><classname>connection</classname></code> object (that will
-    disconnect on destruction). Finally, the mapping from slot groups
-    to slots is based on the key value in a
-    <code><classname>std::multimap</classname></code> (the stored data
-    in the <code><classname>std::multimap</classname></code> is the
-    slot pair).</para>
-  </section>
-
-  <section>
     <title>Slot Call Iterator</title>
 
     <para> The slot call iterator is conceptually a stack of iterator