Closes cpp-netlib#129, Closes cpp-netlib#279, Closes cpp-netlib#27

- Deprecate Synchronous Client implementations (cpp-netlib#279)
- Support Streaming body in Client Request (cpp-netlib#27)
- Deprecate support for header-only usage (cpp-netlib#129)

Author: deanberris

libs/network/doc/reference/http_client.rst

@@ -14,10 +14,6 @@ use and embed in your own applications. All of the HTTP client implementations:
   * **Assume that requests made are independent of each other.** There currently
     is no cookie or session management system built-in to cpp-netlib's HTTP client
     implementations.
-  * **Are header-only and are compiled-into your application.** Future releases in
-    case you want to upgrade the implementation you are using in your application
-    will be distributed as header-only implementations, which means you have to
-    re-compile your application to use a newer version of the implementations.
 
 The HTTP clients all share the same API, but the internals are documented in
 terms of what is different and what to expect with the different
@@ -26,6 +22,9 @@ implementations.
 As of 0.9.1 the default implementation for the :mod:`cpp-netlib` HTTP client is
 asynchronous.
 
+As of 0.11 the `Synchronous Clients`_ are now *DEPRECATED* and will be removed
+in subsequent releases.
+
 Implementations
 ---------------
 
@@ -78,6 +77,9 @@ are encountered in the performance of the HTTP requests.
 .. warning:: The synchronous clients are **NOT** thread safe. You will need to do
    external synchronization to use synchronous client implementations.
 
+.. note:: As of version 0.11, all the synchronous client implementations are
+   deprecated. They will be removed in the next version of the library.
+
 Asynchronous Clients
 ~~~~~~~~~~~~~~~~~~~~
 
@@ -151,6 +153,9 @@ Also, that code using the HTTP client will have use the following header:
    inhibited by defining the ``BOOST_NETWORK_NO_LIB`` preprocessor macro before
    including any cpp-netlib header.
 
+.. note:: Starting version 0.11, cpp-netlib clients and server implementations
+   no longer support the ``BOOST_NETWORK_NO_LIB`` option.
+
 Constructors
 ~~~~~~~~~~~~
 
@@ -264,6 +269,22 @@ and that there is an appropriately constructed response object named
     body chunks be handled by the ``callback`` parameter. The signature of
     ``callback`` should be the following: ``void(iterator_range<char const *> const
     &, boost::system::error_code const &)``.
+``response_ = client_.post(request_, streaming_callback)``
+    Perform and HTTP POST request, and have the request's body chunks be
+    generated by the ``streaming_callback`` which has a signature of the form:
+    ``bool(string_type&)``. The provided ``string_type&`` will be streamed as
+    soon as the function returns. A return value of ``false`` signals the client
+    that the most recent invocation is the last chunk to be sent.
+``response_ = client_.post(request_, callback, streaming_callback)``
+    Perform an HTTP POST request, and have the body chunks be handled by the
+    ``callback`` parameter. The signature of ``callback`` should be the
+    following: ``void(iterator_range<char const *> const &,
+    boost::system::error_code const &)``. This form also has the request's body
+    chunks be generated by the ``streaming_callback`` which has a signature of
+    the form: ``bool(string_type&)``. The provided ``string_type&`` will be
+    streamed as soon as the function returns. A return value of ``false``
+    signals the client that the most recent invocation is the last chunk to be
+    sent.
 ``response_ = client_.put(request_)``
     Perform an HTTP PUT, use the data already set in the request object which
     includes the headers, and the body.
@@ -294,6 +315,22 @@ and that there is an appropriately constructed response object named
     body chunks be handled by the ``callback`` parameter. The signature of
     ``callback`` should be the following: ``void(iterator_range<char const *> const
     &, boost::system::error_code const &)``.
+``response_ = client_.put(request_, streaming_callback)``
+    Perform and HTTP PUT request, and have the request's body chunks be
+    generated by the ``streaming_callback`` which has a signature of the form:
+    ``bool(string_type&)``. The provided ``string_type&`` will be streamed as
+    soon as the function returns. A return value of ``false`` signals the client
+    that the most recent invocation is the last chunk to be sent.
+``response_ = client_.put(request_, callback, streaming_callback)``
+    Perform an HTTP PUT request, and have the body chunks be handled by the
+    ``callback`` parameter. The signature of ``callback`` should be the
+    following: ``void(iterator_range<char const *> const &,
+    boost::system::error_code const &)``. This form also has the request's body
+    chunks be generated by the ``streaming_callback`` which has a signature of
+    the form: ``bool(string_type&)``. The provided ``string_type&`` will be
+    streamed as soon as the function returns. A return value of ``false``
+    signals the client that the most recent invocation is the last chunk to be
+    sent.
 ``response_ = client_.delete_(request_)``
     Perform an HTTP DELETE request.
 ``response_ = client_.delete_(request_, body_handler=callback)``