hi
Brian Moseley wrote:
I guess this would meet the requirements for those
expecting a webDAV server that is (as a first step)
not limited regarding PROPPATCH. Second it would
allow to have a handling of property modifications
which is specific for individual resource types instead
of trying to set all properties to the uppermost node.
seems like a reasonable approach. i think it's important to continue
to store the encoding, media type and last modified timestamp for the
resource even if the underlying node type does not explicitly require
those jcr properties, but assuming that's done, i'm +1.
sure. i don't want to get rid of them.
Maybe i even prefer not to modify the 'DefaultHandler' but
instead change the manager (explicitely setting the nodetypes
while adding the DefaultHandler).
Regarding the property handling i rather think of separate interfaces
and adjusting the implementations present than modifying the existing
IOHandler/IOManager interfaces.
regards
angela
