From 4aaab5b40834583fd9cb692f1bcf30d22b75a00e Mon Sep 17 00:00:00 2001 From: Rich Bowen Date: Tue, 20 Apr 2010 13:02:49 +0000 Subject: [PATCH] Improved XML. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@935897 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/mod_lua.html.en | 60 ++++++++++++++++----------------- docs/manual/mod/mod_lua.xml | 60 ++++++++++++++++----------------- 2 files changed, 60 insertions(+), 60 deletions(-) diff --git a/docs/manual/mod/mod_lua.html.en b/docs/manual/mod/mod_lua.html.en index 428e22e3b6..51c7b0484c 100644 --- a/docs/manual/mod/mod_lua.html.en +++ b/docs/manual/mod/mod_lua.html.en @@ -104,16 +104,18 @@ modules should use the module tag modified time indicates it is newer than the one it has already loaded. The other values cause it to keep the file cached forever (don't stat and replace) or to never cache the - file. + file.

- In general stat or forever is good production and stat or never - for deveopment. +

In general stat or forever is good production and stat or never + for deveopment.

- Examples: - LuaCodeCache stat - LuaCodeCache forever - LuaCodeCache never -

+

Examples:

+ LuaCodeCache stat
+ LuaCodeCache forever
+ LuaCodeCache never
+

+ +
top

LuaHookAccessChecker Directive

@@ -239,12 +241,9 @@ modules should use the module tag match groups into both the file path and the function name be careful writing your regular expressions to avoid security issues.

-

- Examples: -

-

+

Examples:

LuaMapHandler /(\w+)/(/w+) /scripts/$1.lua handle_$2 -

+

This would match uri's such as /photos/show?id=9 to the file /scripts/photos.lua and invoke the handler function handle_show on the lua vm after @@ -269,11 +268,9 @@ modules should use the module tag

Add a path to lua's shared library search path. Follows the same conventions as lua. This just munges the package.cpath in the - lua vms. + lua vms.

- Examples: - LuaPackagePath /scripts/lib/?.so -

+
top

LuaPackagePath Directive

@@ -285,12 +282,13 @@ modules should use the module tag Module:mod_lua

Add a path to lua's module search path. Follows the same conventions as lua. This just munges the package.path in the - lua vms. + lua vms.

- Examples: - LuaPackagePath /scripts/lib/?.lua +

Examples:

+ LuaPackagePath /scripts/lib/?.lua
LuaPackagePath /scripts/lib/?/init.lua -

+

+
top

LuaRoot Directive

@@ -317,23 +315,25 @@ modules should use the module tag Module:mod_lua

Specify the lifecycle scope of the Lua interpreter which will - be used by handlers in this "Directory." The default is "once" + be used by handlers in this "Directory." The default is "once"

+ +
+
once:
use the interpreter once and throw it away.
- once: use the interpreter once and throw it away. - - request: use the interpreter to handle anything based on +
request:
use the interpreter to handle anything based on the same file within this request, which is also - request scoped. + request scoped.
- conn: Same as request but attached to the connection_rec +
conn:
Same as request but attached to the connection_rec
- server: This one is different than others because the +
server:
This one is different than others because the server scope is quite long lived, and multiple threads will have the same server_rec. To accommodate this server scoped interpreter are stored in an apr resource list. The min and max arguments are intended - to specify the pool size, but are unused at this time. -

+ to specify the pool size, but are unused at this time.
+
+
diff --git a/docs/manual/mod/mod_lua.xml b/docs/manual/mod/mod_lua.xml index 47a7a502ed..08c8f21565 100644 --- a/docs/manual/mod/mod_lua.xml +++ b/docs/manual/mod/mod_lua.xml @@ -61,23 +61,25 @@ modules should use the module tag

Specify the lifecycle scope of the Lua interpreter which will - be used by handlers in this "Directory." The default is "once" + be used by handlers in this "Directory." The default is "once"

+ +
+
once:
use the interpreter once and throw it away.
- once: use the interpreter once and throw it away. - - request: use the interpreter to handle anything based on +
request:
use the interpreter to handle anything based on the same file within this request, which is also - request scoped. + request scoped.
- conn: Same as request but attached to the connection_rec +
conn:
Same as request but attached to the connection_rec
- server: This one is different than others because the +
server:
This one is different than others because the server scope is quite long lived, and multiple threads will have the same server_rec. To accommodate this server scoped interpreter are stored in an apr resource list. The min and max arguments are intended - to specify the pool size, but are unused at this time. -

+ to specify the pool size, but are unused at this time.
+
+ @@ -91,12 +93,9 @@ modules should use the module tag match groups into both the file path and the function name be careful writing your regular expressions to avoid security issues.

-

- Examples: -

- + Examples: LuaMapHandler /(\w+)/(/w+) /scripts/$1.lua handle_$2 - +

This would match uri's such as /photos/show?id=9 to the file /scripts/photos.lua and invoke the handler function handle_show on the lua vm after @@ -116,12 +115,13 @@ modules should use the module tag LuaPackagePath /path/to/include/?.lua

Add a path to lua's module search path. Follows the same conventions as lua. This just munges the package.path in the - lua vms. + lua vms.

- Examples: - LuaPackagePath /scripts/lib/?.lua + Examples: + LuaPackagePath /scripts/lib/?.lua
LuaPackagePath /scripts/lib/?/init.lua -

+ + @@ -131,11 +131,9 @@ modules should use the module tag

Add a path to lua's shared library search path. Follows the same conventions as lua. This just munges the package.cpath in the - lua vms. + lua vms.

- Examples: - LuaPackagePath /scripts/lib/?.so -

 + @@ -149,16 +147,18 @@ modules should use the module tag modified time indicates it is newer than the one it has already loaded. The other values cause it to keep the file cached forever (don't stat and replace) or to never cache the - file. + file.

- In general stat or forever is good production and stat or never - for deveopment. +

In general stat or forever is good production and stat or never + for deveopment.

- Examples: - LuaCodeCache stat - LuaCodeCache forever - LuaCodeCache never -

+ Examples: + LuaCodeCache stat
+ LuaCodeCache forever
+ LuaCodeCache never
+ + + -- 2.40.0