The one problem I see with using either the Slide client API or WVCM is user authentication. The user must supply a username and password to authenticate. So if you are writing a portlet to display the contents of the content store you must have access to the user's password. In my environment this is not acceptable. I looked at the Slide server API as a way to get around this problem. What might work real well is to support something like SAML assertions as a method of authentication and identity passing.
Just my two cents. Regards, James James Chamberlain General Dynamics - Advanced Information Systems Prototype Pathway - Collaborative Information Environment U.S. Joint Forces Command [EMAIL PROTECTED] -----Original Message----- From: Michael Oliver [mailto:[EMAIL PROTECTED] Sent: Thursday, June 03, 2004 11:32 AM To: 'Slide Users Mailing List' Subject: RE: Slide API I would concur with Daniel, any performance downside is trivial and in my experience any gains would not be worth the effort and I would doubt would be observable by a user. The big advantage is load balancing so you can use parallel processing in multiple VM's if you use the WebDAV interface whereas you cannot if going directly to the Server API and as Daniel points out you can't do everything with the Server API as yet anyway. Michael Oliver CTO Matrix Intermedia Inc. 3325 N. Nellis Blvd, #1 Las Vegas, NV 89115 Phone:(702)643-7425 Fax:(520)844-1036 Lord, I love you and I need you, come into my heart, and bless me, my family, my home, and my friends, in Jesus' name. Amen -----Original Message----- From: Daniel Florey [mailto:[EMAIL PROTECTED] Sent: Thursday, June 03, 2004 5:22 AM To: Slide Users Mailing List Subject: Re: Slide API 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] --------------------------------------------------------------------- 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]
