How do you guys as the Slide developers envision Slide being used in a portal environment?
Would you recommend embedding Slide into our portal application and using the Slide server APIs (or from what I've heard the WEBDAV level above may be a more appropriate place to integrate)? Or Should we keep Slide separate in it's own web application and connect via the Slide client API or possibly the new WVCM API? I have been using the client API and it's functionality works great for me, the big problem with it for me is the requirement to have the user's username and password. I really want something that can just use the user's Principal. One option we have been considering is running two instances of Slide against the same repository (if this can be done). One instance un-modified so that it can support Microsoft webfolders clients and another with a modified WebdavServlet that we could embed into our portal application and talk to using the end user's Principal. Does this seem reasonable? I know from searching the list that others are wrestling with this same question. I saw one post mentioning that they wanted to wrap Slide with a session bean in Jboss or connect to it via JCA. Someone asked about which portal we are running, we have experimented with Pluto (and we use a modified version of it for testing) and we also use eXo. When Jetspeed 2 gets further along I am sure we will look at it since we have had many successes with Jetspeed 1. Regards, James --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
