doc: added a flow chart for ngx_srcache.

agentzh · agentzh · commit 662c077849c8 · 2014-03-31T17:33:32.000-07:00
diff --git a/README.markdown b/README.markdown
@@ -168,6 +168,10 @@ Usually, [memc-nginx-module](http://github.com/agentzh/memc-nginx-module) is use
 
 For main requests, the [srcache_fetch](#srcache_fetch) directive works at the end of the access phase, so the [standard access module](http://nginx.org/en/docs/http/ngx_http_access_module.html)'s [allow](http://nginx.org/en/docs/http/ngx_http_access_module.html#allow) and [deny](http://nginx.org/en/docs/http/ngx_http_access_module.html#deny) direcives run *before* ours, which is usually the desired behavior for security reasons.
 
+The workflow of this module looks like below:
+
+![srcache flowchart](http://agentzh.org/misc/image/srcache-flowchart.png "srcache flowchart")
+
 [Back to TOC](#table-of-contents)
 
 Subrequest caching
diff --git a/doc/HttpSRCacheModule.wiki b/doc/HttpSRCacheModule.wiki
@@ -102,6 +102,10 @@ Usually, [[HttpMemcModule]] is used together with this module to provide a concr
 
 For main requests, the [[#srcache_fetch|srcache_fetch]] directive works at the end of the access phase, so the [[HttpAccessModule|standard access module]]'s [[HttpAccessModule#allow|allow]] and [[HttpAccessModule#deny|deny]] direcives run ''before'' ours, which is usually the desired behavior for security reasons.
 
+The workflow of this module looks like below:
+
+http://agentzh.org/misc/image/srcache-flowchart.png
+
 == Subrequest caching ==
 
 For ''subrequests'', we explicitly '''disallow''' the use of this module because it's too difficult to get right. There used to be an implementation but it was buggy and I finally gave up fixing it and abandoned it.
