Domain.xml Configuration Node

This node configures the pathes where those objects (in this case actions, users collection, etc...) are stores.

<configuration>
    <!-- Actions mapping -->
    <read-object>/actions/read</read-object>
    <create-object>/actions/write</create-object>
    <remove-object>/actions/write</remove-object>
    <grant-permission>/actions/write-acl</grant-permission>
    <revoke-permission>/actions/write-acl</revoke-permission>
    <read-permissions>/actions/read-acl</read-permissions>
    <read-own-permissions>/actions/read-current-user-privilege-set</read-own-permissions>
    <lock-object>/actions/write</lock-object>
    <kill-lock>/actions/unlock</kill-lock>
    <read-locks>/actions/read</read-locks>
    <read-revision-metadata>/actions/read</read-revision-metadata>
    <create-revision-metadata>/actions/write-properties</create-revision-metadata>
    <modify-revision-metadata>/actions/write-properties</modify-revision-metadata>
    <remove-revision-metadata>/actions/write-properties</remove-revision-metadata>
    <read-revision-content>/actions/read</read-revision-content>
    <create-revision-content>/actions/write-content</create-revision-content>
    <modify-revision-content>/actions/write-content</modify-revision-content>
    <remove-revision-content>/actions/write-content</remove-revision-content>
    <bind-member>/actions/bind</bind-member>
    <unbind-member>/actions/unbind</unbind-member>
    <!-- Paths configuration -->
    <userspath>/users</userspath>
    <rolespath>/roles</rolespath>
    <actionspath>/actions</actionspath>
    <filespath>/files</filespath>
    <parameter name="dav">true</parameter>
    <parameter name="standalone">true</parameter>
    <parameter name="acl_inheritance_type">path</parameter>
    <!-- Nested roles: 0 means no nesting (default), 1 means one sublevel, etc. -->
    <parameter name="nested_roles_maxdepth">0</parameter>
    <!-- Can be "off", "write" and "full" -->
    <parameter name="sequential-mode">full</parameter>
    <!-- "false" lets all read-only methods be executed outside of transactions -->
    <parameter name="all-methods-in-transactions">true</parameter>
    <!-- Setting this to true will force Slide to internally convert the username a user
                 enters at login to lowercase. This is useful for users who can't be bothered
                 with turning off their capslock key before logging in. -->
    <parameter name="force-lowercase-login">false</parameter>
</configuration>

...

all-methods-in-transactions

<parameter name="all-methods-in-transactions">true</parameter>

Supposedly you can set this to "false" to allow read-only methods to execute without being in a transaction. Some initial testing shows this to be somewhat true, but the results are pretty sporadic and may cause your slide instance to be unstable regarding performance (i.e. 1 sec response once, then a 40 sec response another time -- compared to 3 sec static average when set to "true").

ConfigurationNode (last edited 2009-09-20 22:02:43 by localhost)