Hi Marc, my strong advice would be to stay with WVCM or switch to webdavclient-lib. If you are using the Slide api directly, you'll run into trouble. At the moment, some of the repository logic (binding, versioning etc.) is unfortunately coded into the webdav layer. So if you create revisions using the slide api, you cannot access that via deltav lateron. We are currently doing some progress on speeding up the Slide server in general, so: stay with wvcm. Regards , Daniel
[EMAIL PROTECTED] wrote:
Hi,
Currently we are using the WVCM api to access the webdav server. As we looked at the architecture overview documentation of slide, we saw that it is possible for a java application in the same JVM to access directly the slide server api.
This is our case, our business logic for lifecycle management runs inside the same web server. We would like to know if it would be possible to use directly the slide server api and what would be the consequence (improve of performance, functionality available).
Regards
Marc Lefevre
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
