That's indeed the direction I want to go. but I want to start with an interface that is also usable in a client-server environment.
I basically want the same WebDav interface on the server as on the client. For example, you should be able to do: repository.put(path,file) and it shouldn't matter if the repository is local or remote. Those slide-implementation-specific details are very integrated with the pure WebDav part but if you find a nice way split them please do so... but its harder then it looks... Another way to webdav-enable an existing web application is to implement a store that connects to your application. Dirk Kelvin Tan wrote: > > I'm interested in using the WebDav servlet to webdav-enable an existing web >application. Basically act as a server to display existing content through >webdav-clients. > > Looking through WebdavServlet, I found quite alot of references to the Namespaces, >which I understand is Slide's way of tackling content management. What I'm asking >myself if, do these Slide-implementation-specific details such as namespaces and >slidetokens and the lot really belong in WebdavServlet? > > What do you think of creating an interface/abstract base class which represents the >contracts a WebdavServlet has to fulfill, and defer the Slide-specific implementation >to, say, SlideWebdavServlet? > > I'd be willing to work on it if some direction is provided. > > Or maybe I'm missing something really fundamental here... > > Regards, > Kelvin Tan > > Relevanz Pte Ltd > http://www.relevanz.com > > 180B Bencoolen St. > The Bencoolen, #04-01 > S(189648) > > Tel: 238 6229 > Fax: 337 4417 > > Regards, > Kelvin Tan > > Relevanz Pte Ltd > http://www.relevanz.com > > 180B Bencoolen St. > The Bencoolen, #04-01 > S(189648) > > Tel: 238 6229 > Fax: 337 4417 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
