Index: read_write_mutex-ref.xml
===================================================================
RCS file: /cvsroot/boost/boost/libs/thread/doc/read_write_mutex-ref.xml,v
retrieving revision 1.4.10.5
diff -r1.4.10.5 read_write_mutex-ref.xml
39a40,49
>     <note> Unfortunately it turned out that the current implementation of Read/Write Mutex has     
>             some serious problems. So it was decided not to put this implementation into
>             release grade code. Also discussions on the mailing list led to the
>             conclusion that the current concepts need to be rethought. In particular
>             the schedulings <link linkend="thread.concepts.read-write-scheduling-policies.inter-class">
>                 Inter-Class Scheduling Policies</link> are deemed unnecessary.
>             There seems to be common belief that a fair scheme suffices.
>             The following documentation has been retained however, to give
>             readers of this document the opportunity to study the original design.
>     </note>
162a173,182
>     <note> Unfortunately it turned out that the current implementation of Read/Write Mutex has     
>             some serious problems. So it was decided not to put this implementation into
>             release grade code. Also discussions on the mailing list led to the
>             conclusion that the current concepts need to be rethought. In particular
>             the schedulings <link linkend="thread.concepts.read-write-scheduling-policies.inter-class">
>                 Inter-Class Scheduling Policies</link> are deemed unnecessary.
>             There seems to be common belief that a fair scheme suffices.
>             The following documentation has been retained however, to give
>             readers of this document the opportunity to study the original design.
>     </note>
304a325,334
>     <note> Unfortunately it turned out that the current implementation of Read/Write Mutex has     
>             some serious problems. So it was decided not to put this implementation into
>             release grade code. Also discussions on the mailing list led to the
>             conclusion that the current concepts need to be rethought. In particular
>             the schedulings <link linkend="thread.concepts.read-write-scheduling-policies.inter-class">
>                 Inter-Class Scheduling Policies</link> are deemed unnecessary.
>             There seems to be common belief that a fair scheme suffices.
>             The following documentation has been retained however, to give
>             readers of this document the opportunity to study the original design.
>     </note>