<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
+ will have the same server_rec. To accommodate this,
+ server scoped Lua states are stored in an apr
resource list. The <code>min</code> and <code>max</code> arguments
specify the minimum and maximum number of Lua states to keep in the
pool.</dd>
maximum performance. While the <code>thread</code> scope will provide the
fastest responses, the <code>server</code> scope will use less memory, as
states are pooled, allowing f.x. 1000 threads to share only 100 Lua states,
- thus using only 10% of the memory requried by the <code>thread</code> scope.
+ thus using only 10% of the memory required by the <code>thread</code> scope.
</p>
</usage>
</directivesynopsis>
<p>This directive matches a uri pattern to invoke a specific
handler function in a specific file. It uses PCRE regular
expressions to match the uri, and supports interpolating
- match groups into both the file path and the function name
- be careful writing your regular expressions to avoid security
+ match groups into both the file path and the function name.
+ Be careful writing your regular expressions to avoid security
issues.</p>
<example><title>Examples:</title>
<highlight language="config">