> -----Original Message----- > From: Richard Unger [mailto:[EMAIL PROTECTED] > Sent: Friday, January 16, 2004 04:09 > To: Slide Users Mailing List > Subject: RE: Is Slide the best choice ? > > > Quoting Jim Tivy <[EMAIL PROTECTED]>: > > > Hi folks > > > > Why is slide not good for hooking up repositories. Isn't > this what Tamino > > did with slide V1.x? How many other databases/interfaces > have used slide > > for providing WebDav - JDBC to name one? > > > > AFAIK, Tamino stores and indexes XML, so Slide uses Tamino as > a 'Store', and > implements a store class to talk to it. For pure storage, any > repository can > be tied into slide without too much hassle. > What's much harder is integrating a full repository, which > has its own > notions of users, permissions, versions, etc, things that > slide usally > handles.
Right, that's what I would also say. > > As well, isn't it a big mistake to tie the user storage > into slide - what > > about single signon functionality where you rely on a directory or > > authentication server to authenticate users. > > > > I agree with you here. Hm ... it's about authorization too, not only authentication. Also, the WebDAV ACL Standard requires principals to be represented as WebDAV resources. So, it's natural to have them as part of the namespace, IMHO. > > Having slide store permissions is probably OK although it should be > > abstracted if possible. > > > > I am interested because we too have looked at slide > although we currently > > have our own WebDav client. > > > > cheers > > Jim > > > > > -----Original Message----- > > > From: Richard Unger [mailto:[EMAIL PROTECTED] > > > Sent: Thursday, January 15, 2004 9:35 AM > > > To: Slide Users Mailing List > > > Subject: Re: Is Slide the best choice ? > > > > > > > > > > > > > > > Hi! > > > > > > > > > Slide may not be your best choice, it depends. > > > > > > Slide is mainly a content repository, ie slide stores and loads > > > the content, > > > and takes care of versioning and searching etc... From the sounds > > > of things, > > > however, it sounds like you already have the repository, > and only want > to > > > provide webdav access to the existing repository. In this case > > > using slide > > > might be trcky, since presumably you would have to write > a store class > to > > > interface with your existing repository. You'd pretty soon run > > > into issues > > > with users and permissions, since slide expects to store these. > > > > > > It might be easier to use a more simple webdav server, > such as the one > > > bundled with Tomcat. I don't know if this webdav server > expects to read/ > > > write directly from the file system, but assuming it operates on > > > the Tomcat > > > Resource level, all you would have to do is implement a JNDI > > > DirContext to > > > provide read/write access to your existing repository, > and you'd have a > > > solution... > > > > > > > > > Richie > > > > > > > > > > > > Quoting Flavio Eduardo de Cordova <[EMAIL PROTECTED]>: > > > > > > > People... > > > > > > > > I started studying Slide some weeks ago but I have some > > > questions and I > > > hope > > > > you can help me... > > > > > > > > First, my goal is to create a WebDAV layer to > an ECM System (ECM = > > > > Enterprise Content Management) that has all the > information about > users, > > > > permissions, structure, documents and content. When the user > > > connects to > > > this > > > > layer he must see only the folders/documents he's > allowed, exactly > like > > > when > > > > he/she uses the system's web version. > > > > > > > > So, my first question is: Slide has some > default folders in the root > > > > (/actions, /files, etc) that I don't want to show to > the users. Since > > > those > > > > folders are configured in the domain.xml could I remove these > > > entries and > > > use > > > > a new one (for the root) that would get this > information from my ECM > > > system > > > > (for example: <objectnode classname="org.acme.MyNewNodeType" > > > uri="/" />) ? > > > I > > > > know they are important to make slide work properly but > considering > I'm > > > going > > > > to use custom classes should I be concerned ? > > > > If not, how do I do this ? Have somebody used > slide to do > > > something like > > > > this before ? > > > > > > > > I'm not convinced yet if Slide is the best > choice to help > > > me on this > > > since > > > > it looks like I'll have to rewrite a lot of classes... Or maybe > > > it's not > > > so > > > > many but I feel like I'm buying a whole car just to get a new > > > tire. All I > > > > need is somebody to handle the WebDAV protocol.. > > > > > > > > Do you think I should be trying to use any > other component > > > or API ? Or > > > Slide > > > > is actually the best choice ? Have somebody already done this ? > > > > > > > > Flavio Eduardo de C�rdova > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > --------------------------- > > > This mail sent through the > > > ungerground webmail system > > > > > > > --------------------------------------------------------------------- > > > 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] > > > > > > > > > --------------------------- > This mail sent through the > ungerground webmail system > > --------------------------------------------------------------------- > 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]
