diff options
| author | Antoine Beaupré <anarcat@koumbit.org> | 2013-06-19 09:58:35 -0400 |
|---|---|---|
| committer | Antoine Beaupré <anarcat@koumbit.org> | 2013-06-19 09:58:35 -0400 |
| commit | c5ea7ea7c8689cdc00fc379b4ef3ccebb441ebc8 (patch) | |
| tree | 0a8ccf67d7ac61402e912a17c8c92f66a6c47269 | |
| parent | bdb17a6d3070292ae965b73bf318a53bedd3d79a (diff) | |
| download | ikiwiki-c5ea7ea7c8689cdc00fc379b4ef3ccebb441ebc8.tar ikiwiki-c5ea7ea7c8689cdc00fc379b4ef3ccebb441ebc8.tar.gz | |
mention the fastcgi todo here
| -rw-r--r-- | doc/forum/web_service_API__44___fastcgi_support.mdwn | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/forum/web_service_API__44___fastcgi_support.mdwn b/doc/forum/web_service_API__44___fastcgi_support.mdwn index 4a78fb932..84b227eef 100644 --- a/doc/forum/web_service_API__44___fastcgi_support.mdwn +++ b/doc/forum/web_service_API__44___fastcgi_support.mdwn @@ -11,3 +11,8 @@ Anyway - I've realised that a big part of the interactive todo lists stuff is tr Second, and in a way related, I've been mooting hacking fastcgi support into ikiwiki. Essentially one ikiwiki.cgi process would persist and serve CGI-ish requests on stdin/stdout. The initial content-scanning and dependency generation would happen once and not need to be repeated for future requests. Although, all state-changing operations would need to be careful to ensure the in-memory models were accurate. Also, I don't know how suited the data structures would be for persistence, since the current model is build em up, throw em away, they might not be space-efficient enough for persistence. If I did attempt this, I would want to avoid restructuring things in a way which would impair ikiwiki's core philosophy of being a static compiler. -- [[Jon]] + +> This is quite interesting! There is a related discussion about FastCGI +> support (and therefore better support for Nginx, for example) in +> [[todo/fastcgi_or_modperl_installation_instructions/]]... -- +> [[anarcat]] |