property performance question

I am using zero-length files with properties to simulate a tree-store (because
our existing SCM tool works this way), with this example structure:

parent
        child1
        child2
        .
        .
        .
        .svn
                props/prop-base
                        {child1 property files}
                        {child2 property files}

where props/child1.svn-work would have keys like
        prop1
        prop2

Would it be significantly more efficient (in terms of network traffic
minimization/ speed of child property change propagation) for me to just have
this structure

parent
        .svn
                dir-props

where dir-props had keys like
        child1.prop1
        child1.prop2
        child2.prop1
        child2.prop2
and a 'children' property with "child1, child2" as the value?

Before I actually code the change and do comparison tests, I wondered if any
of you had advice. Is there a limit to the size of property files like
dir-props? Are changes to property files sent as deltas during communication
with the subversion server? Any chance of adding a filter argument to
'proplist' to help locate these 'flattened' properties more quickly, eg:
        svn proplist --filter child1.* parent

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 23 19:32:48 2004