You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by am...@apache.org on 2018/05/18 17:27:11 UTC
[trafficserver] branch master updated: For TS remap API functions,
elaborate on mutual exclusion in the documentation.
This is an automated email from the ASF dual-hosted git repository.
amc pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/trafficserver.git
The following commit(s) were added to refs/heads/master by this push:
new 74eb527 For TS remap API functions, elaborate on mutual exclusion in the documentation.
74eb527 is described below
commit 74eb52768423bcded646d480f9b8ce799685fe6e
Author: Walt Karas <wk...@oath.com>
AuthorDate: Tue May 15 18:16:56 2018 +0000
For TS remap API functions, elaborate on mutual exclusion in the documentation.
---
doc/developer-guide/api/functions/TSRemap.en.rst | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/doc/developer-guide/api/functions/TSRemap.en.rst b/doc/developer-guide/api/functions/TSRemap.en.rst
index 77b80f8..38d06d8 100644
--- a/doc/developer-guide/api/functions/TSRemap.en.rst
+++ b/doc/developer-guide/api/functions/TSRemap.en.rst
@@ -69,6 +69,11 @@ the HTTP transaction.
remap configuration file (:file:`remap.config`) is reloaded. This is an optional
entry point, which takes no arguments and has no return value.
+Generally speaking, calls to these functions are mutually exclusive. The exception
+is for functions which take an HTTP transaction as a parameter. Calls to these
+transaction-specific functions for different transactions are not necessarily mutually exclusive
+of each other.
+
Types
=====
--
To stop receiving notification emails like this one, please contact
amc@apache.org.