code style

websocketpp/endpoint.hpp

@@ -348,9 +348,10 @@ public:
 
     /// Get default maximum message size
     /**
-     * Get the default maximum message size that will be used for new connections created
-     * by this endpoint. The maximum message size determines the point at which the
-     * connection will fail a connection with the message_too_big protocol error.
+     * Get the default maximum message size that will be used for new 
+     * connections created by this endpoint. The maximum message size determines
+     * the point at which the connection will fail a connection with the 
+     * message_too_big protocol error.
      *
      * The default is set by the max_message_size value from the template config
      *
@@ -362,9 +363,10 @@ public:
     
     /// Set default maximum message size
     /**
-     * Set the default maximum message size that will be used for new connections created
-     * by this endpoint. Maximum message size determines the point at which the connection
-     * will fail a connection with the message_too_big protocol error.
+     * Set the default maximum message size that will be used for new 
+     * connections created by this endpoint. Maximum message size determines the
+     * point at which the connection will fail a connection with the
+     * message_too_big protocol error.
      *
      * The default is set by the max_message_size value from the template config
      *
@@ -393,21 +395,21 @@ public:
 
     /// Pause reading of new data (exception free)
     /**
-     * Signals to the connection to halt reading of new data. While reading is paused, 
-     * the connection will stop reading from its associated socket. In turn this will 
-     * result in TCP based flow control kicking in and slowing data flow from the remote
-     * endpoint.
+     * Signals to the connection to halt reading of new data. While reading is 
+     * paused, the connection will stop reading from its associated socket. In
+     * turn this will result in TCP based flow control kicking in and slowing
+     * data flow from the remote endpoint.
      *
-     * This is useful for applications that push new requests to a queue to be processed
-     * by another thread and need a way to signal when their request queue is full without
-     * blocking the network processing thread.
+     * This is useful for applications that push new requests to a queue to be 
+     * processed by another thread and need a way to signal when their request
+     * queue is full without blocking the network processing thread.
      *
      * Use `resume_reading()` to resume.
      *
-     * If supported by the transport this is done asynchronously. As such reading may not
-     * stop until the current read operation completes. Typically you can expect to
-     * receive no more bytes after initiating a read pause than the size of the read 
-     * buffer.
+     * If supported by the transport this is done asynchronously. As such
+     * reading may not stop until the current read operation completes. 
+     * Typically you can expect to receive no more bytes after initiating a read
+     * pause than the size of the read buffer.
      *
      * If reading is paused for this connection already nothing is changed.
      */
@@ -418,8 +420,8 @@ public:
 
     /// Resume reading of new data (exception free)
     /**
-     * Signals to the connection to resume reading of new data after it was paused by
-     * `pause_reading()`.
+     * Signals to the connection to resume reading of new data after it was 
+     * paused by `pause_reading()`.
      *
      * If reading is not paused for this connection already nothing is changed.
      */