[interchange-docs] [SCM] Interchange XML documentation branch, master, updated. 84eca367e4415a7502b5975453f2f5051b47c36d
Stefan Hornburg
racke at rt.icdevgroup.org
Tue Apr 21 18:52:53 UTC 2009
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Interchange XML documentation".
The branch, master has been updated
via 84eca367e4415a7502b5975453f2f5051b47c36d (commit)
from be976a759ac0e1cd84b1530527fcce35491fb2e6 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 84eca367e4415a7502b5975453f2f5051b47c36d
Author: Stefan Hornburg (Racke) <racke at linuxia.de>
Date: Tue Apr 21 20:52:12 2009 +0200
DOCUMENTATION FOR:
* Add ability to configure the number of levels and hash length for
the directory structure of file-based sessions. Instead of a fixed
value of 2 and 1 for levels and length, respectively, make two
configuration parameters:
SessionHashLength
SessionHashLevels
Default is 1 and 2, respectively, matching the current values.
This solves the problem of session IDs passed from CGI::Session or other
modules that use a quasi-sequential session ID. You end up placing all
sessions in the S/2 directory for a long time, followed by the S/3 directory,
etc. A setting of:
SessionHashLength 4
SessionHashLevels 1
would break sessions up into separate directories instead of putting all
sessions in a huge directory.
-----------------------------------------------------------------------
Summary of changes and diff:
refs/SessionHashLength | 65 ++++++++++++++++++++++++++++++++++++++++++++++++
refs/SessionHashLevels | 64 +++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 129 insertions(+), 0 deletions(-)
create mode 100644 refs/SessionHashLength
create mode 100644 refs/SessionHashLevels
diff --git a/refs/SessionHashLength b/refs/SessionHashLength
new file mode 100644
index 0000000..a085658
--- /dev/null
+++ b/refs/SessionHashLength
@@ -0,0 +1,65 @@
+__NAME__ purpose
+specify the number of characters to hash session directories
+__END__
+
+
+__NAME__ synopsis
+<arg choice='plain'><replaceable>integer</replaceable></arg>
+__END__
+
+
+__NAME__ see also
+SessionHashLevels
+__END__
+
+
+__NAME__ description
+This directive combiles with SessionHashLevels to configure the number of levels and hash length for
+the directory structure of file-based sessions.
+
+Default is 1.
+
+This solves the problem of session IDs passed from CGI::Session or other
+modules that use a quasi-sequential session ID. You end up placing all
+sessions in the S/2 directory for a long time, followed by the S/3 directory,
+etc. A setting of:
+
+SessionHashLength 4
+SessionHashLevels 1
+
+would break sessions up into separate directories instead of putting all
+sessions in a huge directory.
+__END__
+
+__NAME__ notes
+The default value of 1, combined with SessionHashLevels of 2, creates a
+directory structure like:
+
+<programlisting>
+ 4
+ +----w
+ 6
+ +----r
+ D
+ +----9
+ +----R
+ r
+ +----z
+ s
+ +----s
+ X
+ +----s
+ z
+ +----3
+</programlisting>
+
+__END__
+
+__NAME__ example: Setting SessionExpire
+Put the following in &ccf;:
+<programlisting>
+SessionHashLength 4
+SessionHashLevels 1
+</programlisting>
+__END__
+
diff --git a/refs/SessionHashLevels b/refs/SessionHashLevels
new file mode 100644
index 0000000..7df8626
--- /dev/null
+++ b/refs/SessionHashLevels
@@ -0,0 +1,64 @@
+__NAME__ purpose
+specify the number of levels to hash session directories
+__END__
+
+__NAME__ synopsis
+<arg choice='plain'><replaceable>integer</replaceable></arg>
+__END__
+
+
+__NAME__ see also
+SessionHashLength
+__END__
+
+
+__NAME__ description
+This directive combiles with SessionHashLength to configure the number of levels and hash length for
+the directory structure of file-based sessions.
+
+Default is 1.
+
+This solves the problem of session IDs passed from CGI::Session or other
+modules that use a quasi-sequential session ID. You end up placing all
+sessions in the S/2 directory for a long time, followed by the S/3 directory,
+etc. A setting of:
+
+SessionHashLength 4
+SessionHashLevels 1
+
+would break sessions up into separate directories instead of putting all
+sessions in a huge directory.
+__END__
+
+__NAME__ notes
+The default value of 2, combined with SessionHashLength of 1, creates a
+directory structure like:
+
+<programlisting>
+ 4
+ +----w
+ 6
+ +----r
+ D
+ +----9
+ +----R
+ r
+ +----z
+ s
+ +----s
+ X
+ +----s
+ z
+ +----3
+</programlisting>
+
+__END__
+
+__NAME__ example: Setting SessionExpire
+Put the following in &ccf;:
+<programlisting>
+SessionHashLevels 1
+SessionHashLength 4
+</programlisting>
+__END__
+
hooks/post-receive
--
Interchange XML documentation
More information about the docs
mailing list