You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by rb...@apache.org on 2010/04/20 15:02:49 UTC
svn commit: r935897 - in /httpd/httpd/trunk/docs/manual/mod: mod_lua.html.en
mod_lua.xml
Author: rbowen
Date: Tue Apr 20 13:02:49 2010
New Revision: 935897
URL: http://svn.apache.org/viewvc?rev=935897&view=rev
Log:
Improved XML.
Modified:
httpd/httpd/trunk/docs/manual/mod/mod_lua.html.en
httpd/httpd/trunk/docs/manual/mod/mod_lua.xml
Modified: httpd/httpd/trunk/docs/manual/mod/mod_lua.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_lua.html.en?rev=935897&r1=935896&r2=935897&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_lua.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_lua.html.en Tue Apr 20 13:02:49 2010
@@ -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.</p>
- In general stat or forever is good production and stat or never
- for deveopment.
+ <p>In general stat or forever is good production and stat or never
+ for deveopment.</p>
- Examples:
- LuaCodeCache stat
- LuaCodeCache forever
- LuaCodeCache never
-</p>
+ <div class="example"><h3>Examples:</h3><p><code>
+ LuaCodeCache stat<br />
+ LuaCodeCache forever<br />
+ LuaCodeCache never<br />
+ </code></p></div>
+
+
</div>
<div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
<div class="directive-section"><h2><a name="LuaHookAccessChecker" id="LuaHookAccessChecker">LuaHookAccessChecker</a> <a name="luahookaccesschecker" id="luahookaccesschecker">Directive</a></h2>
@@ -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.</p>
- <p>
- Examples:
- </p>
-<div class="example"><p><code>
+ <div class="example"><h3>Examples:</h3><p><code>
LuaMapHandler /(\w+)/(/w+) /scripts/$1.lua handle_$2
- </code></p></div>
+ </code></p></div>
<p>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
</table>
<p>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.</p>
- Examples:
- LuaPackagePath /scripts/lib/?.so
-</p>
+
</div>
<div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
<div class="directive-section"><h2><a name="LuaPackagePath" id="LuaPackagePath">LuaPackagePath</a> <a name="luapackagepath" id="luapackagepath">Directive</a></h2>
@@ -285,12 +282,13 @@ modules should use the module tag
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_lua</td></tr>
</table><p>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.</p>
- Examples:
- LuaPackagePath /scripts/lib/?.lua
+ <div class="example"><h3>Examples:</h3><p><code>
+ LuaPackagePath /scripts/lib/?.lua<br />
LuaPackagePath /scripts/lib/?/init.lua
-</p>
+ </code></p></div>
+
</div>
<div class="top"><a href="#page-header"><img alt="top" src="/images/up.gif" /></a></div>
<div class="directive-section"><h2><a name="LuaRoot" id="LuaRoot">LuaRoot</a> <a name="luaroot" id="luaroot">Directive</a></h2>
@@ -317,23 +315,25 @@ modules should use the module tag
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_lua</td></tr>
</table>
<p>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"</p>
+
+ <dl>
+ <dt>once:</dt> <dd>use the interpreter once and throw it away.</dd>
- once: use the interpreter once and throw it away.
-
- request: use the interpreter to handle anything based on
+ <dt>request:</dt> <dd>use the interpreter to handle anything based on
the same file within this request, which is also
- request scoped.
+ request scoped.</dd>
- conn: Same as request but attached to the connection_rec
+ <dt>conn:</dt> <dd>Same as request but attached to the connection_rec</dd>
- server: This one is different than others because the
+ <dt>server:</dt> <dd>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.
-</p>
+ to specify the pool size, but are unused at this time.</dd>
+ </dl>
+
</div>
</div>
<div class="bottomlang">
Modified: httpd/httpd/trunk/docs/manual/mod/mod_lua.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_lua.xml?rev=935897&r1=935896&r2=935897&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_lua.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_lua.xml Tue Apr 20 13:02:49 2010
@@ -61,23 +61,25 @@ modules should use the module tag
<usage>
<p>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"</p>
+
+ <dl>
+ <dt>once:</dt> <dd>use the interpreter once and throw it away.</dd>
- once: use the interpreter once and throw it away.
-
- request: use the interpreter to handle anything based on
+ <dt>request:</dt> <dd>use the interpreter to handle anything based on
the same file within this request, which is also
- request scoped.
+ request scoped.</dd>
- conn: Same as request but attached to the connection_rec
+ <dt>conn:</dt> <dd>Same as request but attached to the connection_rec</dd>
- server: This one is different than others because the
+ <dt>server:</dt> <dd>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.
-</p></usage>
+ to specify the pool size, but are unused at this time.</dd>
+ </dl>
+</usage>
</directivesynopsis>
@@ -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.</p>
- <p>
- Examples:
- </p>
-<example>
+ <example><title>Examples:</title>
LuaMapHandler /(\w+)/(/w+) /scripts/$1.lua handle_$2
- </example>
+ </example>
<p>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
<syntax>LuaPackagePath /path/to/include/?.lua</syntax>
<usage><p>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.</p>
- Examples:
- LuaPackagePath /scripts/lib/?.lua
+ <example><title>Examples:</title>
+ LuaPackagePath /scripts/lib/?.lua<br />
LuaPackagePath /scripts/lib/?/init.lua
-</p></usage>
+ </example>
+</usage>
</directivesynopsis>
<directivesynopsis>
@@ -131,11 +131,9 @@ modules should use the module tag
<usage>
<p>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.</p>
- Examples:
- LuaPackagePath /scripts/lib/?.so
-</p></usage>
+</usage>
</directivesynopsis>
<directivesynopsis>
@@ -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.</p>
- In general stat or forever is good production and stat or never
- for deveopment.
+ <p>In general stat or forever is good production and stat or never
+ for deveopment.</p>
- Examples:
- LuaCodeCache stat
- LuaCodeCache forever
- LuaCodeCache never
-</p></usage>
+ <example><title>Examples:</title>
+ LuaCodeCache stat<br />
+ LuaCodeCache forever<br />
+ LuaCodeCache never<br />
+ </example>
+
+</usage>
</directivesynopsis>
<directivesynopsis>