[asterisk-commits] file: branch file/sorcery r378408 - /team/file/sorcery/configs/

[SVN commits to the Asterisk project]

Author: file
Date: Thu Jan  3 09:08:46 2013
New Revision: 378408

URL: http://svnview.digium.com/svn/asterisk?view=rev&rev=378408
Log:
Add sample configuration file with details for sorcery.

Added:
    team/file/sorcery/configs/sorcery.conf.sample   (with props)

Added: team/file/sorcery/configs/sorcery.conf.sample
URL: http://svnview.digium.com/svn/asterisk/team/file/sorcery/configs/sorcery.conf.sample?view=auto&rev=378408
==============================================================================
--- team/file/sorcery/configs/sorcery.conf.sample (added)
+++ team/file/sorcery/configs/sorcery.conf.sample Thu Jan  3 09:08:46 2013
@@ -1,0 +1,50 @@
+; Sample configuration file for Sorcery Data Access Layer
+
+;
+; Wizards
+;
+; Wizards are the object persistence mechanism for objects. They are loaded as Asterisk modules and register
+; themselves with the sorcery core. All implementation specific details of how objects are persisted is isolated
+; within wizards.
+;
+
+;
+; Caching
+;
+; A wizard can optionally be marked as an object cache by adding "/cache" to the object type within the mapping.
+; If an object is returned from a non-object cache it is immediately given to the cache to be created. Multiple
+; object caches can be configured for a single object type.
+;
+
+;
+; Object Type Mappings
+;
+; To allow configuration of where and how an object is persisted object mappings can be defined within this file
+; on a per-module basis. The mapping consists of the object type, options, wizard name, and wizard configuration
+; data. This has the following format:
+;
+; object type [/options] = wizard name, wizard configuration data
+;
+; For example to configure an in-memory wizard for the 'bob' object type:
+;
+; bob = memory
+;
+; Or to configure the object type 'joe' from a configuration file:
+;
+; joe = config,joe.conf
+;
+; Note that an object type can have multiple mappings defined. Each mapping will be consulted in the order in which
+; it appears within the configuration file. This means that if you are configuring a wizard as a cache it should
+; appear as the first mapping so the cache is consulted before all other mappings.
+;
+
+;
+; The following object mappings are used by the unit test to test certain functionality of sorcery.
+;
+[test_sorcery]
+test=memory
+
+[test_sorcery_cache]
+test/cache=test
+test=memory
+

Propchange: team/file/sorcery/configs/sorcery.conf.sample
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: team/file/sorcery/configs/sorcery.conf.sample
------------------------------------------------------------------------------
    svn:keywords = Author Date Id Revision

Propchange: team/file/sorcery/configs/sorcery.conf.sample
------------------------------------------------------------------------------
    svn:mime-type = text/plain