at the moment it is not recommended to use the slide api directly as you don't have access to many features that are hacked into the webdav layer. I don't know if versioning is working by using the slide api, there is some revision support but it is somehow mixed up with the webdav layer, so my advice would be not to use it. If you use slide api you are tied to the same vm so your webapp is not very scalable.
The client library is a good way to access slide as the webdav-layer will not change soo much in future.
WVCM is an abstraction layer on top of webdav, so it is little slower than webdav clientlib but it would be nice, if you would give it a try so that the jsr can get some feedback.
Regards,
Daniel
BTW: Slide is (at the moment) far to slow to serve any webapp in real time.
I'm currently working on a process engine that is doing all the caching and background-building of webpages so that a webapp can be build on top of slide. It will take some weeks until it is at a usable stage, but this might be a choice for webapps in the future.
ryan wrote:
I'm looking at the slide client library, the slide API, and the WVCM API, and I can't figure out which one I should use for a web application. Can someone explain what the difference in these API's is?
Does the Slide API support versioning? Would the Slide API be much faster than the other two because of the network traffic? Which API will support external transactions in the future?
Thanks,
Ryan Rhodes
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
