RE: Slide and JSR170
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]
RE: Slide and JSR170
Thanks for the response. I quess my question is, "What is the overall architecture for CMS as far as Apache goes ?" There seems to be quite a bit of duplication, and I am not sure why slide wouldn't use jackrabbit, or 170. They seem like the logical stack. I agree with your assessment re: webdav. It is more global in nature. Just curious, why do you recommend against using the server Slide API. Is it because it is only relevant to slide ? If so, I agree, because it causes technology lockin. So, if that is the case, what is the benefit of the server api at all ? Jeff -Original Message- From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 30, 2004 6:08 PM To: Slide Users Mailing List; [EMAIL PROTECTED] Subject: Re: Slide and JSR170 Slide does not support JRS170. Jackrabbit isn't used either. It's the other way round as well, Jackrabbit does not use Slide either. I guess there are quite a number of parameters included in the decision which way to go, so I really can not make any recommendation. Good thing about WebDAV is that there already are a number of applications supporting it. Drawback would be that WebDAV by nature is a client/sever protocol, so you would always have the communication overhead. On the other hand while JSR170 covers only certain aspects of a content store, WebDAV is pretty much complete. Additionally, programming against JSR170 would restrict you to Java solutions. I *personally* would not at all recommend programming against the sever Slide API... Oliver On Tue, 30 Nov 2004 17:52:17 -0500, Jeff Broberg <[EMAIL PROTECTED]> wrote: > Ok, simple question. Is the Slide API based on JSR170 ? If so, is > JackRabbit used inside Slide ? We are considering if we should write > our java clients to use WebDAV client protocols or use the Slide API, > or if possible the 170 api. > > Any guidance would be appreciated. > > Jeff > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Slide and JSR170
Ok, simple question. Is the Slide API based on JSR170 ? If so, is JackRabbit used inside Slide ? We are considering if we should write our java clients to use WebDAV client protocols or use the Slide API, or if possible the 170 api. Any guidance would be appreciated. Jeff