AFAIK the Jackrabbit people plan to add WebDAV as well... By the way I see no way why you should not program your management console to the Slide client API that translates your stuff to WebDAV. That one is nice, exists, is easy to program to *and* supports a standard.
Oliver On Wed, 1 Dec 2004 10:27:38 -0500, Jeff Broberg <[EMAIL PROTECTED]> wrote: > Personally, I like the WebDav layer ontop of JSR170. I still feel that > Slide should expose jsr170 as one of its stores, so that it can have > relevance in the long term. I can understand using webdav to access the > content from the client, but to build out a web based management console > ontop of the repository, I do not want a proprietary api ( aka slides ), I > would prefer a standard. At that is where I see 170 being important. > > jeff > > > > -----Original Message----- > From: Carlos Villegas [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 01, 2004 12:39 AM > To: Slide Users Mailing List > Subject: Re: Slide and JSR170 > > kranga wrote: > > I don't think jsr 170 forms a logical stack for Slide - who's primary > > concern is WebDAV protocol implementation. I am very skeptical of jsr > > 170 - more so after looking at participants - Fujitsu, IBM, BEA, Sun, > > HP, Borland aren't exactly companies I think of when considering > > content management systems. I think this is another example of the > > jcp's callous disregard for what already exists. Webdav, Delta V, ACL, > > WebDAV-search etc. already exist as standards in a language neutral > > way. Instead of specifying a java API that basically uses java native > > method calls in lieu of http, they've created a whole parallel spec set. > What a waste ... > > Well, I don't think we're talking about the same things here. Just because > there's SQL, it doesn't mean we don't need JDBC. They are two different > things, WebDAV is a protocol with an underlying model, as you say language > neutral. But to work with it from within a language like java we need an > API. Or else how do you communicate with a WebDAV server from Java. That's > why there's slide-webdavclient, or the slide internal server API. That > jsr170 parallels some of the concepts of WebDAV and related tools is only > natural but it's not a replacement, you can use jsr170 as the java webdav > client API or you can put WebDAV on top of a jsr170 repository server to > expose it remotely. I see it as the same difference as LDAP/JNDI or SQL/JDBC > or XML/SAX/DOM etc. > > Carlos > > --------------------------------------------------------------------- > 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]
