Gianugo Rabellino wrote: > > Unico Hommes wrote: > > > > > Should we strive for strict compatibility in the short term? > > IMO, yes. We are now building a foundation for Cocoon to be a viable DAV > server, and this should include finding all the possible shortcomings > and solve them now instead than later, when we will start polishing > things up. There's always room for hacks, but I'd rather leave them to a > later point: now we're more in a proof of concept phase, after which I > expect some serious design to happen, possibly even on Cocoon core. > > WDYT? >
I agree that for the things we implement we stick to the spec as closely as possible. But I think we will not necessarily want to implement all the features at this time. For instance for COPY and MOVE I don't want to start to implement all the request options and response reports before we have a good way of doing those things. One of the reasons I say this is because we are already running into the limits of our current environment. And before we can really continue we will have to think about how we can solve those issues. But I think you were already hinting towards that. For me, the proof of concept phase is almost over, i.e. I am convinced that building and maintaining a DAV server on top of Cocoon is not only doable it's a very nice fit too. We need to start to take a step back and compare our experiences and come up with a design so that we can start implementing things such as locking, and do PROPFIND, PROPPATCH, MOVE and COPY properly. -- Unico > Ciao, > > -- > Gianugo Rabellino > Pro-netics s.r.l. - http://www.pro-netics.com > Orixo, the XML business alliance - http://www.orixo.com > (Now blogging at: http://blogs.cocoondev.org/gianugo/)
