Added further Policy Framework clarification

[senf.git] / Socket / ClientSocketHandle.hh

diff --git a/Socket/ClientSocketHandle.hh b/Socket/ClientSocketHandle.hh
index 2bd9052..3196967 100644 (file)
--- a/Socket/ClientSocketHandle.hh
+++ b/Socket/ClientSocketHandle.hh
@@ -100,8 +100,9 @@ namespace senf {
         typedef typename Policy::AddressingPolicy::Address Address;
         /// 'Best' type for passing address as parameter
         /** Depending on the type of \c Address, this will be either <tt>Address</tt> or <tt>Address
-            const &</tt>. See <a href="http://www.boost.org/libs/utility/call_traits.htm"
-            class="ext">call_traits documentation in the Boost.Utility library\endlink.</a>
+            const &</tt>. See <a
+            href="http://www.boost.org/libs/utility/call_traits.htm">call_traits documentation in
+            the Boost.Utility library\endlink.</a>
          */
         typedef typename boost::call_traits<Address>::param_type AddressParam;
         /// Corresponding server socket handle with the same policy
@@ -200,7 +201,7 @@ namespace senf {
 
             \returns \c std::pair of data read (a string) and the peers address
 
-            \todo Add \c limit argument
+            \fixme Add \c limit argument
 
             \implementation The readfrom() family of members will use \c recvfrom from the BSD
             socket API.
@@ -243,7 +244,6 @@ namespace senf {
 
             \param[in] data Data to write
             \returns number of bytes written
-            \todo Make this member write the complete string if the socket is blocking
             \implementation The write() family of members will use POSIX \c write calls, not \c
                 send.
          */