From: http://anastigmatix.net/ <http://anastigmatix.net/@web>
Date: Mon, 20 Oct 2014 23:58:54 +0000 (-0400)
Subject: Hadn't listed any drawbacks for the FastCGI Authorizer idea.
X-Git-Tag: 3.20150107~110
X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/commitdiff_plain/34e7fe13e4f60c79de4ee38d6b2d60b08ad411a9?ds=sidebyside;hp=--cc

Hadn't listed any drawbacks for the FastCGI Authorizer idea.
---

34e7fe13e4f60c79de4ee38d6b2d60b08ad411a9
diff --git a/doc/todo/Zoned_ikiwiki.mdwn b/doc/todo/Zoned_ikiwiki.mdwn
index 24fe22133..6b562215a 100644
--- a/doc/todo/Zoned_ikiwiki.mdwn
+++ b/doc/todo/Zoned_ikiwiki.mdwn
@@ -107,6 +107,12 @@ that header might not be needed in the request, and care may be needed to config
 the server to emit other necessary response headers to discourage caching of
 content from a private zone.
 
+*Drawbacks:* Not yet implemented, someone would have to do it.
+It's not clear [[what code changes fastcgi|todo/fastcgi or modperl installation instructions]]
+would require in ikiwiki. An Authorizer seems like a good place to start because of its
+limited, simple functionality--but as it could make use of any ikiwiki-supported auth method,
+evaluate `PageSpec`s, and the like, it could still run a non-trivial amount of the code.
+
 ## Obstacles
 
 A number of ikiwiki features aren't (yet) designed with zoning in mind,