diff options
Diffstat (limited to 'docs/backends/summary.rst')
| -rw-r--r-- | docs/backends/summary.rst | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/docs/backends/summary.rst b/docs/backends/summary.rst index 72b20c9..d648c73 100644 --- a/docs/backends/summary.rst +++ b/docs/backends/summary.rst @@ -3,7 +3,7 @@ Supported backends ================== -sttp suports a number of synchornous and asynchronous backends. It's the backends that take care of managing connections, sending requests and receiving responses: sttp defines only the API to describe the requests to be send and handle the response data. It's the backends where all the heavy-lifting is done. +sttp suports a number of synchronous and asynchronous backends. It's the backends that take care of managing connections, sending requests and receiving responses: sttp defines only the API to describe the requests to be send and handle the response data. It's the backends where all the heavy-lifting is done. Choosing the right backend depends on a number of factors: if you are using sttp to explore some data, or is it a production system; are you using a synchronous, blocking architecture or an asynchronous one; do you work mostly with Scala's ``Future``, or maybe you use some form of a ``Task`` abstraction; finally, if you want to stream requests/responses, or not. @@ -30,3 +30,7 @@ Class Response wrapper Supported stream t ``OkHttpMonixBackend`` ``monix.eval.Task`` ``monix.reactive.Observable[ByteBuffer]`` ================================ ============================ ================================================ +There are also backends which wrap other backends to provide additional functionality. These include: + +* ``TryBackend``, which safely wraps any exceptions thrwon by a synchronous backend in ``scala.util.Try`` +* ``BraveBackend``, for Zipkin-compatible distributed tracing. See the :ref:`dedicated section <brave>`.
\ No newline at end of file |