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]
