Re: Which API should I use for a web app?

[Daniel Florey]

[EMAIL PROTECTED] wrote:

If you use the slide API for storing data from your app, take into 
account that it is reallly complicated to store content in a way that 
you can use the versioning stuff, because all of the versioning is done 
     

in the webdav layer. 

What do you mean ? The slide API can manage NodeRevisionDescriptors and
NodeRevisionDescriptor.
It is not what you expect to do ? or are you speaking about other features ?
 

It would make me happy if you're right. I have not checked it yet, but 
from the parts of the code that I've seen I can't imagine that you can 
access revisions via deltaV if you create them by simply adding new 
revisions via slide api. Can you?
Regards,
Daniel

For fast content retrieval in the same vm, slide 
API might be a good choice.
     

I'm using the Slide API from a Jetspeed service and its works fine. We have
-/+ 20.000 documents and no problem at all.
Maybe, if we have more and more documents, this solution will not be
scalable. So, next plan is to access to different "external" repositories
via the webdav client.
Christophe

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
.

 



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]