Daniel Shahaf wrote: > * ra_dav: I don't know about this one. > > From the neon/serf side, adding the optional "expected preexisting > value" should be straightforward (just another tag/attribute). > > From the mod_dav_svn side, however, the propchanges/propdeletes come > from db_store/db_remove (respectively), and I don't know/see how > mod_dav_svn could obtain the optional "expected preexisting value" > (even if it were present in the request). > > Could someone teach me how mod_dav_svn might be able to obtain the > optional "expected preexisting value"?
Could it get stuffed into the dav_db structure? Does mod_dav open and close the DAV properties database exactly once per PROPPATCH? -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
