Alterator meta-backend uses a place on the filesystem as a persistent
store for object state. Each object represented as a *.scm file
containing an association list of object properties. Sub-objects are
placed in subdirectories.

Meta-backend can be accessed as a normal backend via Woo-bus and has
the base name "/meta". Filesystem place is determined by the remaining
part of the object name, i.e. "/meta/etc/metalterator/db1/obj1"
references a file /etc/metalterator/db1/obj1.scm.

The root object "/meta" properties are reserved for meta-backend itself
and represent meta-backend internal properties. To look inside an object
reading/writing process set property 'debug-level of the "/meta" backend
to a positive (1-5) value. Debugging messages can then be seen at the
`alteratord' console.

The (alterator metalterator) Guile module provides helpful procedures
for meta-backend communication.

• Paul Wolneykien

• metalterator