The folder to store session files in instead of using the local collection repository. 

If null or empty, files will be stored in a central data folder which is the preferred setting.

The maximum number of seconds data can be held in memory before it is flushed to disk. 

In addition to the automatic flush due to the amount of information waiting to be written out the messenger will automatically flush to disk based on the number of seconds specified.

The number of seconds between index updates. 

An index is maintained of session information including the number and types of messages and session status.  It is updated automatically when a session is stopped and in certain other cases.  This setting will control how often updates are published outside of these cases.

The maximum number of megabytes in a single file before a new file is started.

When the file reaches the maximum size it will be closed and a new file started. Due to compression effects and other data storage considerations, final files may end up slightly larger on disk or somewhat smaller.  Setting to zero will allow files to grow to the maximum size allowed by the file format (1 GB) or the maxLocalDiskUsage, whichever is less.

Once a file is closed it will be sent to the server if autoSendSessions is enabled.

The maximum number of minutes in a single file before a new file is started.

When the file reaches the maximum age it will be closed and a new file started.  Setting to zero will allow the file to cover an unlimited period of time.

Once a file is closed it will be sent to the server if autoSendSessions is enabled.

When true, files will be pruned for size or age.

By default, files older than a specified number of days are automatically deleted and the oldest files are removed when the total storage of all files for the application exceeds a set value.  Setting this option to false will disable all pruning.

The maximum number of megabytes for all files for the current application on the local drive before older files are purged.

When the maximum local disk usage is approached, files are purged by selecting the oldest files first.  This limit may be exceeded temporarily by the maximum file size because the active file will not be purged.  Size is specified in megabytes.  Files are purged first by looking for the oldest sessions and then the oldest file fragments for an active session if necessary.

The maximum number of days that session files for the current application are retained.

Session files that were closed longer than the retention interval ago will be removed regardless of space constraints. 

The minimum amount of free disk space in megabytes on the session destination drive for any logging to be performed.

If the amount of free disk space falls below this value, existing session files will be removed to free space.  If no more session files are available, recording will stop until adequate space is available.  Size is specified in megabytes.

When true, all writes will be performed synchronously.  This will ensure they are committed to disk before the next message is processed.

This can affect the degree of parallelism of a multithreaded application and throughput, so is generally only set in cases when the application is crashing during startup or other hard to catch scenarios.

The maximum number of queued messages waiting to be written to disk.

Once the total number of messages waiting to be written exceeds the maximum queue length the log writer will switch to a synchronous mode to catch up.  This will not cause the application to experience synchronous logging behavior unless the publisher queue is also filled.