From 6e109a964383bfe5e2be04f65fa7cc1356a97cbe Mon Sep 17 00:00:00 2001 From: adamw Date: Tue, 17 Oct 2017 17:28:50 +0200 Subject: More docs --- docs/backends/custom.rst | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) (limited to 'docs/backends/custom.rst') diff --git a/docs/backends/custom.rst b/docs/backends/custom.rst index 86d750a..4dd5208 100644 --- a/docs/backends/custom.rst +++ b/docs/backends/custom.rst @@ -1,11 +1,9 @@ +.. _custombackends: + Custom backends, logging, metrics ================================= -It is also entirely possible to write your own backend (if so, please consider -contributing!) or wrapping an existing one. You can even write completely -generic wrappers for any delegate backend, as each backend comes equipped -with a monad for the response type. This brings the possibility to ``map`` and -``flatMap`` over responses. +It is also entirely possible to write custom own backend (if doing so, please consider contributing!) or wrapping an existing one. One can even write completely generic wrappers for any delegate backend, as each backend comes equipped with a monad for the response type. This brings the possibility to ``map`` and ``flatMap`` over responses. Possible use-cases for wrapper-backend include: @@ -13,7 +11,7 @@ Possible use-cases for wrapper-backend include: * capturing metrics * request signing (transforming the request before sending it to the delegate) -To pass some context to wrapper-backends, requests can be *tagged*. Each -``RequestT`` instance contains a ``tags: Map[String, Any]`` field. This is unused -by http, but can be used e.g. to pass a metric name or logging context. +To pass some context to wrapper-backends, requests can be *tagged*. Each ``RequestT`` instance contains a ``tags: Map[String, Any]`` field. This is unused by http, but can be used e.g. to pass a metric name or logging context. + +Example backend logging -- cgit v1.2.3