On 4/6/06, Angela Schreiber <[EMAIL PROTECTED]> wrote: [snip] > > > Proposed solution > ----------------------------------------------------- > > The situation described before leads me to the > following conclusion: > > - IOHandler should not only read/write resource data > and properties during GET, PUT, PROPFIND but should > also take care of setting/removing properties without > modifying the data during PROPPATCH. > > - Since the previous suggestion would still limit > the properties to (jcr:encoding, jcr:mimeType and > jcr:lastModified), we may think about changing the > default nodetype for the jcr:content node to > nt:unstructured. > > 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. > > what do you think?
Hi I don't know enought the jcr, so i can't tell you if the node chose is the best, but I trust you for making the right choice. For allowing the propatch to modify the properties, I agree. so +1 Jérémi -- Blog: http://www.jeremi.info LinkedIn: https://www.linkedin.com/profile?viewProfile=&key=1437724 Project Manager XWiki: http://www.xwiki.org skype: jeremi23 -- msn et gtalk : [EMAIL PROTECTED]
