> 1. What is the difference between protocol-oriented and > resource-oriented?
Protocol-oriented mainly means using the commons/httpclient API enriched by the classes in org.apache.webdav.lib.methods. The app is responsible for creating XML request bodies and parsing XML response bodies and everything is possible. Resource-oriented means working with the classes in org.apache.webdav.lib and org.apache.webdav.lib.properties, mainly WebdavResource. Not everything is possible, e.g. I don't see full support for the marshalling of the CHECKIN request (keep-checked-out, fork-ok). > 2. Where are javax.wvcm.* + org.apache.wvcm.* currently > implemented in the > Slide client? I did not see them yet? (Sorry if they were > added recently, I a > on a CVS from some weeks ago.) The JSR-147 API is not integrated in Slide client but a separate independent component with its own build, currently located in CVS under jakarta-slide/proposals/wvcm. > 3. What would be the benefit of building on javax.wvcm.* + > org.apache.wvcm.* > rather than org.apache.webdav.lib.*. 1) WVCM is (or hopefully will be) standard. 2) All the marshalling of the DeltaV methods is mapped in the WVCM object model. Regards, Peter
